From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6492 Path: news.gmane.org!not-for-mail From: stephen Turner Newsgroups: gmane.linux.lib.musl.general Subject: issues with headers? Date: Thu, 13 Nov 2014 17:02:54 -0500 Message-ID: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2d9dca0a5740507c4accb X-Trace: ger.gmane.org 1415916196 5204 80.91.229.3 (13 Nov 2014 22:03:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Nov 2014 22:03:16 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6505-gllmg-musl=m.gmane.org@lists.openwall.com Thu Nov 13 23:03:09 2014 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Xp2Tt-0001Wd-A8 for gllmg-musl@m.gmane.org; Thu, 13 Nov 2014 23:03:09 +0100 Original-Received: (qmail 7339 invoked by uid 550); 13 Nov 2014 22:03:07 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 7327 invoked from network); 13 Nov 2014 22:03:06 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=gf7QvGSt7It9Y6E4+1pATaJdYe6nEuf8QR0MUfQvv1Q=; b=TEHJcFmmRncsUUYelqqPXxALGLC6/R2VUozvm1JJ4X7rgbSTJd2x2XyQU8mpdyZHVN K0NBbKB+lFcMo4c54ekzff2lLQjmBd2JBV2+YnbpC9pBJ/+y6Wl5ogpI7Bw54VEzJ5Re w6Psr7EJpIg7dmW+FaKnNBj6qluRu6AYs74vjwwH6sjDq38DSH8KEjOupRlh95a7YUwF XJlxbAvQg9APYq30lmGoK2l/tiulyuV1s1WBkAgU4kaKOIkn5D4TAUePhlC+dy/EjnKq TIaGBg5M8Y1BNFUdB14n1fIK65pPClETj5dGaTB/JHrinl4LEZGjWwcgsWDKzSn4+w31 59mA== X-Received: by 10.182.56.163 with SMTP id b3mr4108516obq.54.1415916174744; Thu, 13 Nov 2014 14:02:54 -0800 (PST) Xref: news.gmane.org gmane.linux.lib.musl.general:6492 Archived-At: --001a11c2d9dca0a5740507c4accb Content-Type: text/plain; charset=UTF-8 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. PS: I have found that GCC-4.7.3, GCC-4.8.3, both have the issue thanks, Stephen --001a11c2d9dca0a5740507c4accb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 agains= t 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 m= usl 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&#= 39;t linking against the headers) =C2=A0I first started to see this issue w= hen 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.

PS: I have found= that GCC-4.7.3, GCC-4.8.3, both have the issue

th= anks,
Stephen
--001a11c2d9dca0a5740507c4accb--