public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
To: Chris Morgan <chmorgan@gmail.com>
Cc: crossgcc@sourceware.org, Johannes Stezenbach <js@sig21.net>,
	"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Subject: Re: CLooG build error
Date: Fri, 27 Jan 2012 00:03:00 -0000	[thread overview]
Message-ID: <124943f2-aec3-4fd7-b1e2-6daae43d2dad@zose-store-12> (raw)
In-Reply-To: <CAAPegz3Yv1qSp4_xj3o464YJ633H9Gi17h6K_jZG8KrmSmRqvg@mail.gmail.com>

Hi Chris,

> From: "Chris Morgan" <chmorgan@gmail.com>
> To: "Johannes Stezenbach" <js@sig21.net>
> Cc: crossgcc@sourceware.org
> Sent: Thursday, January 26, 2012 10:23:39 PM
> Subject: Re: CLooG build error
>
> Oh right. I didn't know if it was something in cloog or not.
>
> I got past that error after rebuilding and reinstalling but again a
> failure in cloog after a ct-ng clean and ct-ng build:
>
> in.lo matrix.lo pprint.lo program.lo statement.lo version.lo  -lgmp
> -lppl_c -lppl -lgmpxx -lstdc++
> [ALL  ]    libtool: link: x86_64-build_unknown-linux-gnu-ar cru
> .libs/libcloog.a  block.o loop.o names.o options.o clast.o domain.o
> matrix.o pprint.o program.o statement.o version.o
> [ALL  ]    libtool: link: x86_64-build_unknown-linux-gnu-ranlib
> .libs/libcloog.a
> [ALL  ]    libtool: link: ( cd ".libs" && rm -f "libcloog.la" && ln
> -s
> "../libcloog.la" "libcloog.la" )
> [ALL  ]    make[1]: Leaving directory
> `/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/build-cloog-ppl'
> [EXTRA]    Checking CLooG/ppl
> [DEBUG]    ==> Executing: 'make' '-j2' '-s' 'check'
> [ALL  ]    Making check in .
> [ALL  ]    libtool: link: x86_64-build_unknown-linux-gnu-gcc -Wall
> -fomit-frame-pointer -pipe -o cloog cloog.o
> -L/home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/lib
> ./.libs/libcloog.a -lm
> /home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/lib/libppl_c.a
> /home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/lib/libppl.a
> /home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/lib/libgmpxx.a
> /home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/lib/libgmp.a
> -lstdc++
> [ALL  ]    /usr/bin/ld:
> /home/cmorgan/ct-ng-install/bin/.build/arm-unknown-eabi/build/static/lib/libppl_c.a(ppl_c_implementation_common.o):
> undefined reference to symbol 'fesetround@@GLIBC_2.2.5'
> [ALL  ]    /usr/bin/ld: note: 'fesetround@@GLIBC_2.2.5' is defined in
> DSO
> /usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../x86_64-linux-gnu/libm.so
> so try adding it to the linker command line
> [ALL  ]
>    /usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../x86_64-linux-gnu/libm.so:
> could not read symbols: Invalid operation
> [ALL  ]    collect2: ld returned 1 exit status
> [ERROR]    make[2]: *** [cloog] Error 1
> [ERROR]    make[1]: *** [check-recursive] Error 1
> [ERROR]
> [ERROR]  >>
> [ERROR]  >>  Build failed in step 'Installing CLooG/ppl'
> [ERROR]  >>        called in step '(top-level)'
> [ERROR]  >>
> [ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@172]
> [ERROR]  >>        called from:
> do_cloog[scripts/build/companion_libs/cloog.sh@65]
> [ERROR]  >>        called from: main[scripts/crosstool-NG.sh@597]
> [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]  >>
> '/home/cmorgan/ct-ng-install/share/doc/crosstool-ng/ct-ng.hg@default-188d58cfe7cf/B
> - Known issues.txt'
> [ERROR]
>
> I'm surprised these kinds of things aren't being caught earlier. Is
> there no automated regression suite in crosstool-ng that builds all
> of
> these targets on a daily basis? I'd like to help out since last time
> I
> tried ct-ng it failed for other reasons :-)
>
> Chris

It is possible that you are encountering another consequence of this issue:
http://sourceware.org/ml/crossgcc/2011-12/msg00051.html
http://sourceware.org/ml/crossgcc/2011-12/msg00052.html

Yann has not yet reviewed my patch.

Can you test and report if it solves your issue?

Best regards,
Benoît

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

  reply	other threads:[~2012-01-27  0:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAPegz3+cnkhtdzA1MO8caoH-MXAT6GjPDd6g7cUQ5Moetk2kg@mail.gmail.com>
     [not found] ` <CAAPegz20kka=E=vZ11UB9F8JNFyWpX6NDyzo38K7G1SnVo9a+g@mail.gmail.com>
2012-01-25 22:07   ` Chris Morgan
2012-01-26 15:41     ` Johannes Stezenbach
2012-01-26 15:46       ` Chris Morgan
2012-01-26 16:28         ` Johannes Stezenbach
2012-01-26 21:24           ` Chris Morgan
2012-01-27  0:03             ` Benoît Thébaudeau [this message]
2012-01-27 10:56               ` Johannes Stezenbach
2012-01-27 12:02                 ` Benoît Thébaudeau
2012-01-27 17:18                   ` Chris Morgan
2012-01-27 20:10                     ` Benoît Thébaudeau
2012-01-27 20:06                   ` Chris Morgan
2012-01-27 20:11                     ` Benoît Thébaudeau
2012-01-27 20:15                       ` Chris Morgan
2012-01-27 17:15                 ` Chris Morgan
2012-01-28 23:07       ` Yann E. MORIN
2012-01-29 10:10         ` Johannes Stezenbach
2012-01-29 10:53           ` Yann E. MORIN
2012-01-30 21:16             ` Chris Morgan
     [not found] <5c2d9079-5714-4600-829c-08365856a158@zose-store-12>
2012-01-28 22:41 ` Benoît Thébaudeau

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=124943f2-aec3-4fd7-b1e2-6daae43d2dad@zose-store-12 \
    --to=benoit.thebaudeau@advansee.com \
    --cc=chmorgan@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=js@sig21.net \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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).