From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARM release compiler broken for mpg123.
Date: Fri, 23 Jan 2009 21:37:46 +0100 [thread overview]
Message-ID: <87eiytkbc5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1232723429.5311.73.camel@elrond.atmel.com> (Ulf Samuelsson's message of "Fri\, 23 Jan 2009 16\:10\:29 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Ulf> ?Have been struggling with mpg123 last night.
Ulf> There seems to be a bug in the release version
Ulf> (gcc-4.3.2/bu-2-19/uclibc-0.9.30)
Ulf> of the toolchain which creates a Segment violation.
Ulf> Anyone else can build mpg123, maybe for another architecture?
Yes, it builds on atleast powerpc without problems (afaik also i386,
but that has been a while).
Ulf> I have found an upstream patch, which I will test
Ulf> and apply if it seems to solve the problem.
I guess you'll need to patch the compiler instead as it's the compiler
ICE'ing. Any change you do to mpg123 won't make that bug go away.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-23 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 15:10 [Buildroot] ARM release compiler broken for mpg123 Ulf Samuelsson
2009-01-23 20:37 ` Peter Korsgaard [this message]
2009-01-23 21:08 ` Ulf Samuelsson
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=87eiytkbc5.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.