Date: Tue, 3 May 2016 20:16:20 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com, j-core@...ore.org Subject: Re: musl-cross-make / litecross improvements On Tue, May 03, 2016 at 11:57:05PM +0200, Szabolcs Nagy wrote: > * Szabolcs Nagy <nsz@...t70.net> [2016-05-03 22:16:22 +0200]: > > * Rich Felker <dalias@...c.org> [2016-05-03 14:02:30 -0400]: > > > On Tue, May 03, 2016 at 01:39:43PM +0200, Szabolcs Nagy wrote: > > > > i think the usr/ and lib64/ symlinks are useful > > > > (so it can be used as rootfs without fiddling > > > > with etc/ld-musl*.path). > > > > > > Yes. Is there a good way to override that in gcc or should we just > > > make the symlinks? > > > > > > > output/lib64 can be eliminated by > > COMMON_CONFIG += --libdir=/lib This does not seem useful except for deuglifying; that dir is not part of the target root. > > output/x86_64-linux-musl/lib64 install path is trickier: > > it is controlled by the $toolexeclibdir make variable. > > which is set according to $CC -print-multi-os-directory > > which is controlled by multilib and multilib_defaults from > > $CC -dumpspecs which comes from multilib.h generated by > > genmultilib based on parameters from config/i386/t-linux64 > > it was not clear if the t-linux64 thing could be overridden, but > > GCC_CONFIG += --with-multilib-list= > > fixes it (the lib dir is lib/ then). I wonder if this works for all targets, and how it relates to --disable-multilib. At least on sh4 if you disable multilib you need to --enable-incomplete-targets because the kernel is built with -m4-nofpu and gcc normally errors out when you pass that option and the libs aren't built. I seem to recall multilib options being a mess on some other archs too. Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.