[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] Mikro GCC 4.4.2 build Library Paths
On Monday 11 January 2010, Mark Duckworth wrote:
> I figured this out because I was building something that used this path
> in the la file to try to find the library. I'm not sure why because if
> you look it seems to specify what that library depends on.
Right. But .la files should be purged from the packages created from
a source build, there are more appropriate methods for declaring
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
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
> On 1/10/10 5:32 PM, Miro Kropacek wrote:
> > Question is, is this any bad? I mean, I must build it in some
> > directory while cross compiling, there's no difference if it would be
> > in /usr/local/m68kmint or anything else or?
> > On Sat, Jan 9, 2010 at 5:32 PM, Mark Duckworth
> > <email@example.com <mailto:firstname.lastname@example.org>>
> > wrote:
> > Hey guys,
> > The .la files of mikro's build point to /home/mikro/......
> > Thanks,
> > Mark
> > --
> > MiKRO / Mystic Bytes
> > http://mikro.atari.org