From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: Godmar Back <godmar@gmail.com>
Cc: crossgcc@sourceware.org
Subject: Re: ct-ng build fails with 'make[1]: *** [configure-binutils] Error 1'
Date: Fri, 04 Sep 2009 22:20:00 -0000 [thread overview]
Message-ID: <200909050020.13964.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <719dced30909041203tc20450esa7d8a2c9883f7f8c@mail.gmail.com>
Godmar,
All,
On Friday 04 September 2009 21:03:16 Godmar Back wrote:
> > Yes, some of the components in the toolchain require those updated versions.
> > There has recently been discussions on this list whether it'd make sense
> > for crosstool-NG to build its own version, to alleviate the problem.
> To be clear: in this situation, I'm trying to build a cross compiler
> on a shared platform that I do not administer. So I can't put anything
> in, say /etc/ld.so.conf, /usr/bin, or /usr/lib, or even /usr/local.
> That's why I installed these versions of automake/autoconf in
> $prefix/bin where $prefix is the --prefix argument to ct-ng. I then
> prepend this directory to the path when running ct-ng.
That's all perfectly fine. I was just pointing out that it was a known
situation.
> > did you forget to set the
> > "Target OS" to "linux"?
> I did not - setting x86_64 was the only change I made. I have now
> remedied that and made two changes:
> - target to x86_64
> - OS to Linux.
Well, building a toolchain does not go with the snap of fingers.
As I said previously, there is *no* *sane* defaults to the config
options. So you can *not* rely on just setting a few options here
and there, you have to look at (almost) every other options...
> Now the build fails with:
[--SNIP--]
> build.log shows:
> [ALL ] make[1]: *** No rule to make target
> `../build-i386-build_redhat-linux-gnu/libiberty/libiberty.a', needed
> by `build/genmodes'. Stop.
Did you google for this error?
> All I am interested in is getting a compiler that emits x86_64
> assembly code for some ISO-C code for instructional purposes. It
> doesn't need to run. It doesn't need a particular libc version. I'm
> not picky.
> Do you know of a configuration that is known to work?
The bundled sample x86_64-unknown-linux-uclibc would seem to fit.
How to use samples:
ct-ng "put the sample name here"
Eg. in this case:
ct-ng x86_64-unknown-linux-uclibc
How to list all available samples:
ct-ng list-samples
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ___ |
| --==< ^_^ >==-- `------------.-------: 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
next prev parent reply other threads:[~2009-09-04 22:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 3:47 Godmar Back
2009-09-04 8:49 ` building patched gcc ng
2009-09-04 12:54 ` Thomas Petazzoni
2009-09-04 15:16 ` Yann E. MORIN
2009-09-04 15:07 ` ct-ng build fails with 'make[1]: *** [configure-binutils] Error 1' Yann E. MORIN
2009-09-04 19:03 ` Godmar Back
2009-09-04 22:20 ` Yann E. MORIN [this message]
2009-09-05 14:13 ` Godmar Back
2009-09-06 13:06 ` Yann E. MORIN
2009-09-06 13:34 ` Godmar Back
2009-09-06 13:39 ` Yann E. MORIN
2009-09-07 14:04 ` Godmar Back
2009-09-07 16:06 ` Yann E. MORIN
2009-09-09 13:31 ` Godmar Back
2009-09-09 19:56 ` Yann E. MORIN
[not found] ` <719dced30909092215qe1bf9a2i1d7f10f15733e11c@mail.gmail.com>
2009-09-10 5:16 ` Godmar Back
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=200909050020.13964.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=godmar@gmail.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).