Re: [MiNT] Native GCC built

[Miro Kropáček <miro.kropacek@gmail.com>]

On Mon, Nov 25, 2013 at 6:42 AM, Vincent Rivière <vincent.riviere@freesbee.fr> wrote:

When do I do that?

IIRC, one of them was the bzip2 package, it provides also its own lib.

 

I guess that ncurses is the only one, I should fix it. Anyway, my initial goal was to provide the binaries (clear, reset, etc.) and not the libs (as I wasn't interested by native development).
I the other packages, there are a few lib dirs, but I didn't care of them. It means that multilibs are not provided, and the default one is for the target specfic CPU. Even if they are not complete, those ones are compatible with your new convention.

That's my point, exactly. If you don't care about multilib (and I can understand that), then it makes more sense to put libraries in <prefix>/lib and not <prefix>/<cpu>lib, cpu >= m68020-60. Because if I'm a FB user, I download the FB package and in that case, libs are in <prefix>/lib (and binaries in <prefix>/bin). Same as if I'm a m68020-60 user, my libs are again in <prefix>/lib. Having the cpu directories is useful only for the case you'd like to download m68020-60 bzip and install it on, say, m68000 filesystem what is kind of pointless as <prefix>/bin would contain incompatible executables.

--
MiKRO / Mystic Bytes
http://mikro.atari.org