public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Tor Krill <tor@codeknot.com>, Grant Edwards <grant.b.edwards@gmail.com>
Subject: Re: ct-ng: uClibc build fails: missing libgcc_eh.a for me as well
Date: Tue, 30 Aug 2011 16:19:00 -0000	[thread overview]
Message-ID: <201108301819.21070.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <1314719670.2364.72.camel@tor-desktop>

Tor, Grant, All,

On Tuesday 30 August 2011 17:54:30 Tor Krill wrote:
> I'm trying to build gcc 4.4.6, uclibc 0.9.32 linux-2.6.29.4 or
> linux-2.6.39.4 for a arm based board (Atmel at91).
> 
> I have tried both on a 64 and 32 bit ubuntu 10.10 and i used ct-ng
> 1.12.1
> 
> As Grant Edwards
> (http://sourceware.org/ml/crossgcc/2011-08/msg00024.html) i get:

Yeah, I saw it too, but did not have time to reply... Sorry...
See below...

> [ALL  ]      STRIP -X --strip-debug -R .note -R .comment lib/libpthread.a
> [ALL  ]      LD ld-uClibc-0.9.32.1-git.so
> [ALL  ]    arm-unknown-linux-uclibcgnueabi-gcc: libgcc_eh.a: No such file or directory
> [ERROR]    make[1]: *** [lib/ld-uClibc.so] Error 1
> [ALL  ]    make[1]: *** Waiting for unfinished jobs....
> [ALL  ]      STRIP -x -R .note -R .comment lib/libc.a
> [ALL  ]    make[1]: Leaving directory `/home/tor/build/toolchain/.build/arm-unknown-linux-uclibcgnueabi/build/build-libc'
> [ERROR]    
> [ERROR]    >>  Build failed in step 'Installing C library'
> [ERROR]    >>
> [ERROR]    >>  Error happened in: CT_DoExecLog[scripts/functions]
> [ERROR]    >>        called from: do_libc[scripts/build/libc/uClibc.sh@196]
> [ERROR]    >>        called from: main[scripts/crosstool-NG.sh@588]
> [ERROR]    >>
> [ERROR]    >>  For more info on this error, look at the file: 'build.log'
> [ERROR]    >>  There is a list of known issues, some with workarounds, in:
> [ERROR]    >>      '/usr/local/share/doc/ct-ng-1.12.1/B - Known issues.txt'
> [ERROR]    
> [ERROR]    Build failed in step 'Installing C library'
> [ERROR]    
> [ERROR]    (elapsed: 9:54.92)
> 
> (Backing down to uClibc 0.9.30.3 seems to work.)
> 
> Am I doing something wrong or is this a bug?

What about the patch suggested in that message:
  http://lists.uclibc.org/pipermail/uclibc/2011-June/045411.html

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

  reply	other threads:[~2011-08-30 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 15:54 Tor Krill
2011-08-30 16:19 ` Yann E. MORIN [this message]
2011-08-30 19:37   ` Tor Krill

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=201108301819.21070.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=crossgcc@sourceware.org \
    --cc=grant.b.edwards@gmail.com \
    --cc=tor@codeknot.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).