From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Error building arm toolchain: undefined reference to `raise'
Date: Wed, 1 Nov 2006 11:53:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20061101T124730-455@post.gmane.org> (raw)
In-Reply-To: 4541C1B0.8080408@free-electrons.com
Michael Opdenacker <michael-lists@...> writes:
>
> Philippe Ney wrote:
> > Have a look at the gumstix buildroot (www.gumstix.org) for a patch called
> > uClibc-gcc-41-raise-error.patch, I think this will do the trick.
> >
> To save time, here's the exact location of this patch:
> http://svn.gumstix.com/gumstix-buildroot/trunk/
toolchain/uClibc/uClibc-gcc-41-raise-error.patch
>
> Cheers,
>
> Michael.
>
When/How does this patch (and other similar) get incorporated
into uClibC.org patches ?
Surely that is the most appropriate location ?
Regards,
MikeW
next prev parent reply other threads:[~2006-11-01 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:45 [Buildroot] Error building arm toolchain: undefined reference to `raise' Tor Krill
2006-10-26 19:26 ` Philippe Ney
2006-10-27 6:06 ` Tor Krill
2006-10-27 8:22 ` Michael Opdenacker
2006-11-01 11:53 ` MikeW [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-26 17:48 Michael Opdenacker
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=loom.20061101T124730-455@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--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.