Re: [MiNT] Mikro GCC 4.4.2 build Library Paths

[Eero Tamminen <oak@helsinkinet.fi>]

Hi,

On Tuesday 12 January 2010, Paul Wratt wrote:
> On Tue, Jan 12, 2010 at 10:25 AM, Eero Tamminen <oak@helsinkinet.fi> > > 
One reason why they're evil is that at least in in systems using shared
> > libraries, they cause also indirect dependencies being directly linked
> > into the binary which means that the directly dependencies dependencies
> > cannot be remove/changed.
> >
> > This is bad from package management point of view on such systems.
> > I'm not sure how much of a problem this could be on a system using
> > static libs.
>
> That does imply the possibility of HUGE binaries, outside of the
> normal debug hugeness.

When building static binaries, compiler skips unreferenced objects.

I was thinking possible problem with static libs being more about .la files
in dev packages trying to link obsolete/non-existing indirect libraries, but
that should be much rarer than the issue on systems like Debian which have
large amount of shared libs and deps between them.


> Is there any way to check for these?

On Linux?  Yes.


	- Eero