public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/21782] configure: error: unknown endianess
Date: Mon, 30 May 2005 13:02:00 -0000 [thread overview]
Message-ID: <20050530130123.3629.qmail@sourceware.org> (raw)
In-Reply-To: <20050527123604.21782.papadopo@shfj.cea.fr>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-05-30 13:01 -------
> We're heading in the wrong direction.
>
> I don't see how '-v' can help. The problem is just that LD_LIBRARY_PATH contains
> /usr/local/lib which contains a link to the 32-bit libgcc_s.so.1 library of gcc
> 4.
The problem is that conftest is not supposed to depend on libgcc_s so it would
be nice to print the link command line. Try also to add -static-libgcc to the
GCC command line.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21782
next prev parent reply other threads:[~2005-05-30 13:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 12:38 [Bug libffi/21782] New: " papadopo at shfj dot cea dot fr
2005-05-27 12:40 ` [Bug libffi/21782] " papadopo at shfj dot cea dot fr
2005-05-27 12:50 ` papadopo at shfj dot cea dot fr
2005-05-27 13:18 ` pinskia at gcc dot gnu dot org
2005-05-27 13:37 ` papadopo at shfj dot cea dot fr
2005-05-27 13:44 ` pinskia at gcc dot gnu dot org
2005-05-27 13:50 ` papadopo at shfj dot cea dot fr
2005-05-27 13:59 ` papadopo at shfj dot cea dot fr
2005-05-27 14:40 ` ebotcazou at gcc dot gnu dot org
2005-05-30 7:55 ` papadopo at shfj dot cea dot fr
2005-05-30 9:35 ` ebotcazou at gcc dot gnu dot org
2005-05-30 9:38 ` papadopo at shfj dot cea dot fr
2005-05-30 9:40 ` ebotcazou at gcc dot gnu dot org
2005-05-30 10:34 ` ebotcazou at gcc dot gnu dot org
2005-05-30 10:51 ` ebotcazou at gcc dot gnu dot org
2005-05-30 11:22 ` papadopo at shfj dot cea dot fr
2005-05-30 11:41 ` papadopo at shfj dot cea dot fr
2005-05-30 12:43 ` ebotcazou at gcc dot gnu dot org
2005-05-30 12:44 ` papadopo at shfj dot cea dot fr
2005-05-30 12:58 ` papadopo at shfj dot cea dot fr
2005-05-30 13:00 ` papadopo at shfj dot cea dot fr
2005-05-30 13:02 ` ebotcazou at gcc dot gnu dot org [this message]
2005-05-30 14:40 ` ebotcazou at gcc dot gnu dot org
2005-05-30 14:46 ` [Bug libffi/21782] [3.3 Regression] " pinskia at gcc dot gnu dot org
2005-05-30 14:47 ` ebotcazou at gcc dot gnu dot org
2005-05-30 14:51 ` [Bug bootstrap/21782] " ebotcazou at gcc dot gnu dot org
2005-05-31 16:29 ` ebotcazou at gcc dot gnu dot org
2005-06-02 1:12 ` pinskia at gcc dot gnu dot org
2005-06-02 1:16 ` aaronw at net dot com
2005-06-02 4:39 ` ebotcazou at gcc dot gnu dot org
2005-06-03 21:22 ` aaronw at net dot com
2005-06-03 21:47 ` ebotcazou at gcc dot gnu dot org
2005-06-15 3:25 ` pinskia at gcc dot gnu dot org
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=20050530130123.3629.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).