public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, bonzini@gnu.org
Subject: Re: Massive breakage with your libgcc patches
Date: Thu, 03 Nov 2011 18:15:00 -0000	[thread overview]
Message-ID: <yddd3d92hye.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4EB2D4EF.8090903@codesourcery.com> (Bernd Schmidt's message of	"Thu, 03 Nov 2011 18:52:47 +0100")

Bernd Schmidt <bernds@codesourcery.com> writes:

[Trimming the Cc: list.]

> On 11/03/11 18:01, Rainer Orth wrote:
>> Bernd Schmidt <bernds@codesourcery.com> writes:
>>> A cross environment for -elf targets typicaly just requires building up
>>> binutils/newlib, and that should be rather quick to set up. A set of
>> 
>> Maybe in theory, but for the case at hand, a c6x-elf configuration with
>> binutils from the top of the binutils 2.22 branch fails to configure
>> libgcc:
>> 
>> checking whether to use setjmp/longjmp exceptions... unknown
>> configure: error: unable to detect exception model
>> make[1]: *** [configure-target-libgcc] Error 1
>
> That does not appear to be happening here, neither with 2.22 nor CVS
> head. Please verify how you configured and built binutils and gcc.

Nothing unusual AFAICS:

$ /vol/src/gnu/binutils/binutils-2.22-branch/configure --prefix=/var/gcc/c6x-elf --target c6x-elf
$ PATH=/var/gcc/c6x-elf/bin:$PATH /vol/gcc/src/hg/trunk/local/configure --target c6x-elf --with-gmp=/vol/gcc --without-ppl --without-cloog --enable-languages=c --with-gnu-as --with-as=/var/gcc/c6x-elf/bin/c6x-elf-as --with-gnu-ld --with-ld=/var/gcc/c6x-elf/bin/c6x-elf-ld

All on x86_64-unknown-linux-gnu.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2011-11-03 18:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 17:53 CFT: [build] Move crtstuff support to toplevel libgcc Rainer Orth
2011-08-15 21:00 ` Hans-Peter Nilsson
2011-08-16 17:13   ` Rainer Orth
2011-11-02 12:49 ` Rainer Orth
2011-11-02 20:16   ` Massive breakage with your libgcc patches Hans-Peter Nilsson
2011-11-02 20:26     ` Bernd Schmidt
2011-11-03 13:17       ` Rainer Orth
2011-11-03 13:58         ` Bernd Schmidt
2011-11-03 17:28           ` Rainer Orth
2011-11-03 17:54             ` Bernd Schmidt
2011-11-03 18:15               ` Rainer Orth [this message]
2011-11-03 18:48                 ` Bernd Schmidt
2011-11-03 19:31                   ` Rainer Orth
2011-11-04 12:01                     ` Bernd Schmidt
2011-11-07 13:46                     ` Bernd Schmidt
2011-11-07 18:38                       ` Rainer Orth
2011-11-08 13:27                         ` Paolo Bonzini
2011-11-21 16:41                           ` Rainer Orth
2011-11-21 16:46                             ` Paolo Bonzini
2011-11-08 16:56                         ` Bernd Schmidt
2011-11-08 18:02                           ` Rainer Orth
2011-11-29 16:22                         ` Bernd Schmidt
2011-11-29 16:28                           ` Paolo Bonzini
2011-11-03 13:14     ` Rainer Orth
2011-11-03 14:46       ` Hans-Peter Nilsson
2011-11-03 15:42       ` Hans-Peter Nilsson
2011-11-03 15:42         ` Rainer Orth
2011-11-02 21:29   ` CFT: [build] Move crtstuff support to toplevel libgcc Jason Merrill
2011-11-02 21:47     ` Jason Merrill
2011-11-03 13:07     ` Rainer Orth
2011-11-03 13:12       ` Paolo Bonzini
2011-11-03 16:09         ` Jason Merrill
2011-11-03 11:01   ` Andreas Schwab
2011-11-03 11:37   ` Matthew Gretton-Dann
2011-11-03 16:42     ` Rainer Orth
2011-11-04 13:43   ` Andreas Krebbel
2011-11-04 14:34     ` Rainer Orth
2011-11-04 14:38     ` Andreas Krebbel
2011-11-04 14:54       ` Rainer Orth

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=yddd3d92hye.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=bernds@codesourcery.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.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).