[TriLUG] how to copy librarys and there link structures.

[tj]

nothing wrong with "static" in general.
as my understanding, making static is easy at the beginning, and hard
to maintan afterward.

if you need to put in chroot/ jailed, you can  use static as  you like
for a quick fix, and move to non static in the real production.

speaking of embedded systems. I never create linked-staticly  in the
real production:
let imagine...:
1)  we have limited space and  enough memory in embedded systems.
2) we have   multpile running Daemons on the background.
3) we need to provide on how to update the system ( aka flashing firmware).
4) we try to avoid to create/compile/build all the  programs that
linked statically.
5) we have very minimalistic in hadrware perspective for Embedded system.
6) the last but not the least: how we do debugging.

those are my  understanding. and my common senses.

honestly, easy to maintain non embedded system than embedded system it's self.

we need to concern about the system "env", linked statically is not
copy and run on  some scenario.

as in open source world, we can decide  what is the best fit for our
scenario. that is the spirit of open source:D.



those are my understanding, and  could  be not fit with yours ....

On Wed, Apr 7, 2010 at 2:17 PM, Rodney Radford <rradford at mindspring.com> wrote:
>
> I am curious why you would state that - what is wrong with static in this case?
>
> I understand that it will make the application larger, and that the extra size cannot be shared with other processes like a library.  However, if the intent is to run a single (or limited) number of processes within a jail, it could actually take up less space - both on the disk and in memory - than copying over all the libraries.
>
> So while it is not generally a good idea... for some applications, like the one mentioned here, or embedded systems (as I do), it is a great idea.
>
> Rodney
>
> -----Original Message-----
>>From: tj <bimasakti at gmail.com>
>>Sent: Apr 7, 2010 1:22 PM
>>To: Triangle Linux Users Group General Discussion <trilug at trilug.org>
>>Subject: Re: [TriLUG] how to copy librarys and there link structures.
>>
>>compile into static is not recommended, unless there is  the last option :D
>>
>>On Sun, Apr 4, 2010 at 10:41 PM, Rodney Radford <rradford at mindspring.com> wrote:
>>>
>>> First, run ldd <executable> to see what libraries are needed by the intended executable, and then simply copy each of them to a directory inside your chroot area and point your library path (environment variable LDDPATH) at that directory when you chroot.
>>>
>>> Another option may be to link the program as static and then you don't need to worry about the libraries.
>>>
>>>
>>> -----Original Message-----
>>>>From: Ralph Blach <chipperb at nc.rr.com>
>>>>Sent: Apr 4, 2010 10:25 PM
>>>>To: Triangle Linux Users Group General Discussion <trilug at trilug.org>
>>>>Subject: [TriLUG] how to copy librarys and there link structures.
>>>>
>>>>Is there an easy way to copy librarys and there link structurs?
>>>>
>>>>I need to set up a chroot on my system
>>>>
>>>>Thanks
>>>>
>>>>Chip
>>>>--
>>>>TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
>>>>TriLUG FAQ          : http://www.trilug.org/wiki/Frequently_Asked_Questions
>>>
>>> --
>>> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
>>> TriLUG FAQ          : http://www.trilug.org/wiki/Frequently_Asked_Questions
>>>
>>--
>>TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
>>TriLUG FAQ          : http://www.trilug.org/wiki/Frequently_Asked_Questions
>
> --
> TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG FAQ          : http://www.trilug.org/wiki/Frequently_Asked_Questions
>