there was an devel-m4.diff patch available from gregorr website where the gcc musl patch can be found albiet the m4 was in a different directory and didn't work. https://github.com/GregorR/musl-pkgsrc-patches/blob/master/devel-m4.diff I attached the config.log from the gmp folder. It complains when trying to run -std=c99 or -std=gnu99 -E On Fri, Nov 14, 2014 at 6:37 PM, Matias A. Fonzo wrote: > El Fri, 14 Nov 2014 15:22:28 -0500 > stephen Turner escribió: > > looks like i missed the patch for m4, again my mistake sorry. > > Question, which patch of m4?. > > > thanks, > > stephen > > > > On Fri, Nov 14, 2014 at 3:01 PM, stephen Turner > > wrote: > > > > > It appears like gmp doesn't play nice with musl hosts? a musl > > > target is fine allowing a cross environment to work but not a pure > > > musl evnironment or specifying musl as the host. > > > > > > I created a cross compiler successfully but using the cross > > > compiler to "recreate itself" hasn't worked when rebuilding gmp as > > > a part of the process. It could be me, everything up to this point > > > has been apparently but i was hoping someone could chime in and let > > > me know if they have compiled gmp on a native musl system or if it > > > requires a patch i missed or some gnu code? > > > > > > thanks, > > > stephen > > > > > > On Fri, Nov 14, 2014 at 2:49 PM, stephen Turner < > > > stephen.n.turner@gmail.com> wrote: > > > > > >> GMP errors out with "invalid configuration 'non-pc-linux-musl' not > > >> recognized. Im using the --target and --host flags i686-linux-musl > > >> and --build i686-linux-gnu. I also tried switching to a chroot > > >> musl env and running a plain configure on gmp only and it > > >> complains the compiler cant create executables which i know to be > > >> false. > > >> > > >> Will GMP compile on a musl system? > > >> Google search showed one other person with the issue but no answer. > > >> > > >> thanks, > > >> stephen > > >> > > >> > > >> > > >> On Thu, Nov 13, 2014 at 6:23 PM, stephen Turner < > > >> stephen.n.turner@gmail.com> wrote: > > >> > > >>> It looks like your right, I just ran a compile specifying musl > > >>> headers and this time it worked. I need to review my process yet > > >>> again and see what changed that fixed this issue. > > >>> > > >>> I new this wouldn't be easy but man i didn't expect it to feel > > >>> this finicky or fickle. > > >>> > > >>> thanks, > > >>> stephen > > >>> > > >>> On Thu, Nov 13, 2014 at 5:13 PM, Justin Cormack < > > >>> justin@specialbusservice.com> wrote: > > >>> > > >>>> On Thu, Nov 13, 2014 at 10:02 PM, stephen Turner > > >>>> wrote: > > >>>> > I have been trying various ways of compiling a musl system > > >>>> > using gcc > > >>>> and > > >>>> > found that GCC-4.7.3 does not seem to want to compile against > > >>>> > musl > > >>>> headers. > > >>>> > I install the linux headers in /usr/include then i install > > >>>> > musl and > > >>>> move its > > >>>> > headers to /usr/include. then i specify -I/usr/include to gcc > > >>>> > and it > > >>>> errors > > >>>> > every time (technically its /cross/usr/include as i have a > > >>>> > separated > > >>>> env > > >>>> > from my host system) The same compile works fine against musl > > >>>> > libs > > >>>> but not > > >>>> > the headers. The only change made from a working to a > > >>>> > non-working > > >>>> system > > >>>> > appears to be the use of the musl generated headers. > > >>>> > > > >>>> > In the scripts to build a musl toolchain (such as gregorr) the > > >>>> > header location is not specified but sysroot is used (which > > >>>> > obviously isn't > > >>>> linking > > >>>> > against the headers) I first started to see this issue when > > >>>> chroot'ing into > > >>>> > a newly created musl gcc system. > > >>>> > > > >>>> > Is musl suitable as a stand alone libc replacement? Should i > > >>>> > not be > > >>>> building > > >>>> > against musl headers? If there is any reports or details you > > >>>> > want me > > >>>> to > > >>>> > provide please let me know. > > >>>> > > >>>> You want to use a chroot or a VM with Musl if you are having > > >>>> these issues. Sabotage or Alpine are good options. It will save > > >>>> a lot of grief. Otherwise you are doing somethnig wrong that is > > >>>> hard to diagnose without much moer info. > > >>>> > > >>>> Justin > > >>>> > > >>> > > >>> > > >> > > > > >