RE: Building MIPS Toolchain

[Eric Amirault <eric dot amirault at phybridge dot com>]

Yann, Bryan:
  That fixed the problem. I was able to build the toolchain last night and 
then use it to build busybox. Thanks again.

Eric Amirault
Director of Engineering
Phybridge Inc.
3495 Laird Rd. Unit 12
Mississauga, ON
L5L 5S5
905-901-3633 x106
________________________________________
From: Yann E. MORIN [yann.morin.1998@anciens.enib.fr]
Sent: Friday, October 08, 2010 6:45 PM
To: crossgcc@sourceware.org
Cc: Bryan Hundven; Eric Amirault
Subject: Re: Building MIPS Toolchain

Eric, Bryan,

On Friday 08 October 2010 23:49:08 Bryan Hundven wrote:
> On Fri, Oct 8, 2010 at 2:42 PM, Eric Amirault <eric.amirault@phybridge.com>
> wrote:
> > I am building a MIPS toolchain on an openSUSE 11.1 system using ct-ng
> > version 1.8.2.
> > I get the following error:
[--SNIP--]
> > [ALL ] In file included from ../sysdeps/unix/sysv/linux/syslog.c:10:
> > [ALL ] ../misc/syslog.c: In function '__vsyslog_chk':
> > [ALL ] ../misc/syslog.c:123: sorry, unimplemented: inlining failed in call
> > to 'syslog': function body not available
> see:
> http://sourceware.org/ml/crossgcc/2010-10/msg00021.html

Indeed.

> Would it be possible to add this to the (e)glibc.sh build script? Or
> the list faq?

Would you care sending a patch that either:
  - adds an entry in the known issues
or ( preferred! ;-) ):
  - adds a config knob in the (e)glibc common config menu
  - handles that config knob in the (e)glibc build scripts

Regards,
Yann E. MORIN.

--
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq