Date: Sun, 07 Apr 2013 18:04:47 +0200 From: John Spencer <maillist-musl@...fooze.de> To: musl@...ts.openwall.com Subject: Re: Building libc separately from libm,librt,libpthread and others On 04/07/2013 05:43 PM, Szabolcs Nagy wrote: > * John Spencer<maillist-musl@...fooze.de> [2013-04-07 16:52:08 +0200]: > >> On 04/07/2013 04:43 PM, Timerlan Moldobaev wrote: >> >>> I suppose that might be caused by including in libc.a object files that >>> belong to libm, librt, libpthread and others. >>> Am I right ? >>> Is there any way to compile libc.a solely ? >> the only thing that can theoretically be left away is libm, but this >> would need some effort. >> things like pthread support are fundamental to musl's inner >> workings, so they can not be left away. >> > you can easily drop src/complex (nothing uses that, you are lucky if it > compiles with 4.1 at all, some ppl reported internal compiler errors on > old gccs in the complex code) musl compiles fine with gcc 3.4.6 and gcc 4.2.4 (used by sabotage for stage0 bootstrap - gcc 4.2.4 is only used on arm though) > > if you only want to compile libc.a you can redefine ALL_LIBS in your > config.mak so it does not contain the SHARED_LIBS (see the Makefile) the official way to do this is ./configure --disable-shared
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.