Re: ct-ng build fails with 'make[1]: *** [configure-binutils] Error 1'

[Godmar Back <godmar at gmail dot com>]

On Fri, Sep 4, 2009 at 11:07 AM, Yann E.
MORIN<yann.morin.1998@anciens.enib.fr> wrote:

Yann, thanks for your answer.

>
> On Friday 04 September 2009 05:47:13 Godmar Back wrote:
>> When building ct-ng, it indicated that my automake and autoconf were
>> out-of-date (that, by itself, triggered repressed memories...)
>> So I downloaded and configured autoconf-2.64 and automake-1.10.2 with
>> the same prefix into which I installed ct-ng.
>
> 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.
>
> I haven't had time to look into this, but it's on the tablets...

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.

>
> Tuples in the form arch-vendor-elf are for bare-metal. Are you sure
> you want to run on bare-metal x86-64? Are 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.

Now the build fails with:
[INFO ]  Installing shared core C compiler
[ERROR]    Build failed in step 'Installing shared core C compiler'
[ERROR]    Error happened in
'/home/courses/cs3214/cross-x86_64/lib/ct-ng-1.4.2/scripts/functions'
in function 'CT_DoExecLog' (line unknown, sorry)
[ERROR]          called from
'/home/courses/cs3214/cross-x86_64/lib/ct-ng-1.4.2/scripts/build/cc/gcc.sh'
at line # 213 in function 'do_cc_core'
[ERROR]          called from
'/home/courses/cs3214/cross-x86_64/lib/ct-ng-1.4.2/scripts/build/cc/gcc.sh'
at line # 69 in function 'do_cc_core_pass_2'
[ERROR]          called from
'/home/courses/cs3214/cross-x86_64/lib/ct-ng-1.4.2/scripts/crosstool-NG.sh'
at line # 497 in function 'main'
[ERROR]    Look at
'/home/courses/cs3214/x-tools/x86_64-unknown-linux-gnu/build.log' for
more info on this error.
[ERROR]  (elapsed: 25:00.40)
[25:01] / make: *** [build] Error 2

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.
[ALL  ]    make[1]: Leaving directory
`/home/courses/cs3214/software/crossbuild/targets/x86_64-unknown-linux-gnu/build/build-cc-core-shared/gcc'

Full log is:
http://courses.cs.vt.edu/~cs3214/crosstools-ng/build.log
.config is:
http://courses.cs.vt.edu/~cs3214/crosstools-ng/dot.config

>
> Hmm.. There is no "default" configuration for crosstool-NG. There are so
> many possibilities, depending on so many factors, that deciding upon a
> sane default is not easy. For the "Target OS", the default is "bare metal"
> which alphabetically sorts before "linux"
>
> That's bad because the sorting can be different, depending on the locale
> in use... But I consider this as being a minor issue (if at all), and
> I didn't look at /fixing/ it.
>

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?

 - Godmar

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