mailing list of musl libc
 help / color / mirror / code / Atom feed
From: stephen Turner <stephen.n.turner@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Musl and pcc
Date: Thu, 7 May 2015 14:07:49 -0400	[thread overview]
Message-ID: <CAA7aPHhuor30TUfXwXtpA_ryCctQLMDNyj+iuiZ0Wrpp-fJk8g@mail.gmail.com> (raw)
In-Reply-To: <20150507165122.GU17573@brightrain.aerifal.cx>


[-- Attachment #1.1: Type: text/plain, Size: 1025 bytes --]

Todays version using a script, pcc-$(date +%Y%m%d).tgz but any version from
the past couple days would do it.

I attached the script which is the same thing i have used in the past to
build my custom chroot. Its set to build infinitely so i tend to babysit it
just in case the issue has been fixed but i like to run it once a day to
see how things are working. The build breaks on the 2nd build (first in a
chroot)




On Thu, May 7, 2015 at 12:51 PM, Rich Felker <dalias@libc.org> wrote:

> On Thu, May 07, 2015 at 12:26:37PM -0400, stephen Turner wrote:
> > Rich, i know you guys have made some good changes recently to pcc and to
> > musl. I see my compiles with the latest pcc and musl-1.1.8 are getting
> much
> > farther along then previously. I'm currently seeing a error message "
> > include/stdint.h:84 error: bad terminal L'\0' " Does this sound like a
> > issue you guys were running into?
>
> I've never seen this issue. Presumably it's a bug in the preprocessor.
> What version of pcc are you using?
>
> Rich
>

[-- Attachment #1.2: Type: text/html, Size: 1536 bytes --]

[-- Attachment #2: bootstrap.sh --]
[-- Type: application/x-sh, Size: 9249 bytes --]

  reply	other threads:[~2015-05-07 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 16:26 stephen Turner
2015-05-07 16:51 ` Rich Felker
2015-05-07 18:07   ` stephen Turner [this message]
2015-05-08 22:27     ` stephen Turner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA7aPHhuor30TUfXwXtpA_ryCctQLMDNyj+iuiZ0Wrpp-fJk8g@mail.gmail.com \
    --to=stephen.n.turner@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).