From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "acrux@cruxppc.org" <acrux@linuxmail.org>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] powerpc: 405/440/464/476 support and optimizations
Date: Thu, 19 Jan 2012 19:35:00 -0000 [thread overview]
Message-ID: <CADZpyiwX0-Ydc2BVOxohe=+iVgGzHBn6Cra8bhpT28A1-FkeWw@mail.gmail.com> (raw)
In-Reply-To: <33163939.post@talk.nabble.com>
On Wed, Jan 18, 2012 at 3:30 PM, acrux@cruxppc.org <acrux@linuxmail.org> wrote:
>
> just tried to build glibc-2.13 "--with-cpu=440 --with-fp" on a Sam440ep[1]
> (PPC440EP SoC [2]) but it remains stuck in this point:
> CPP='gcc -m32 -E -x c-header' /home/999/new/work/src/build32/elf/ld.so.1
> --library-path
> /home/999/new/work/src/build32:/home/999/new/work/src/build32/math:/home/999/new/work/src/build32/elf:/home/999/new/work/src/build32/dlfcn:/home/999/new/work/src/build32/nss:/home/999/new/work/src/build32/nis:/home/999/new/work/src/build32/rt:/home/999/new/work/src/build32/resolv:/home/999/new/work/src/build32/crypt:/home/999/new/work/src/build32/nptl
> /home/999/new/work/src/build32/sunrpc/rpcgen -Y ../scripts -c
> rpcsvc/bootparam_prot.x -o
> /home/999/new/work/src/build32/sunrpc/xbootparam_prot.T
This is the first use of the newly build dynamic loader.
A failure here means that the dynamic loader has not been correctly compiled.
You should debug this to figure out what is going wrong in the loader.
> Here my config.log: http://cruxppc.org/~acrux/config.log
> Instead i successfully built glibc-2.13 without "--with-cpu=440 --with-fp" .
> I'm using an updated CRUX PPC 2.7 (32bit): gcc-4.5.3, binutils-2.21.1,
> glibc-2.12.2
Have you tested your compiler? What were the test results?
Did you test binutils? What were the test results?
Cheers,
Carlos.
next prev parent reply other threads:[~2012-01-19 19:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 17:34 Luis Machado
2010-09-03 14:45 ` Ryan Arnold
2010-09-03 15:00 ` Luis Machado
2010-10-04 18:54 ` Luis Machado
2010-12-13 20:26 ` Ryan Arnold
2011-01-18 13:16 ` Ryan Arnold
2011-01-25 21:32 ` Joseph S. Myers
2012-01-18 20:31 ` acrux@cruxppc.org
2012-01-19 19:35 ` Carlos O'Donell [this message]
2012-01-20 14:24 ` acrux
2012-01-20 15:52 ` Ryan S. Arnold
2012-01-20 18:03 ` Carlos O'Donell
2012-01-23 0:41 ` acrux
2012-01-23 15:48 ` Ryan S. Arnold
2012-01-24 16:47 ` acrux
2012-01-24 17:20 ` Ryan S. Arnold
2012-01-24 17:41 ` acrux
2012-01-24 17:59 ` Ryan S. Arnold
2012-02-18 2:06 ` acrux
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='CADZpyiwX0-Ydc2BVOxohe=+iVgGzHBn6Cra8bhpT28A1-FkeWw@mail.gmail.com' \
--to=carlos@systemhalted.org \
--cc=acrux@linuxmail.org \
--cc=libc-ports@sourceware.org \
/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).