Date: Sun, 14 Apr 2013 21:31:54 -0400 From: Rich Felker <dalias@...ifal.cx> To: musl@...ts.openwall.com Subject: Request for ideas on arch-specific musl-gcc specfile additions Right now, musl-gcc has problems on at least a few archs: - powerpc: it does not setup the right secure-plt options for dynamic linking. - mips: gcc's internals on mips expect the -EL and -EB options to work for selecting endianness, but they're not real options; they're created by the specfile - any arch with 32/64-bit variants: if -m32 or -m64 was used building musl, it should get added to the specfile for musl-gcc. I'm looking for a clean approach to fixing this. Certainly the configure script could just generate one or more extra variables that get stored in config.mak and substituted into the specfile, but I'd rather avoid having essential logic like this in configure, as it makes it difficult for anybody who wants to generate config.mak by hand. If there are specific options always needed on a given arch, the build process (even without configure being used) should automatically add them to the specfile. Any good proposals? 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.