public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "papadopo at shfj dot cea dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/21782] configure: error: unknown endianess
Date: Mon, 30 May 2005 07:55:00 -0000	[thread overview]
Message-ID: <20050530075104.609.qmail@sourceware.org> (raw)
In-Reply-To: <20050527123604.21782.papadopo@shfj.cea.fr>


------- Additional Comments From papadopo at shfj dot cea dot fr  2005-05-30 07:50 -------
This program builds just fine:

$ cat > conftest.c
main () {
  /* Are we little or big endian?  From Harbison&Steele.  */
  union
  {
    long l;
    char c[sizeof (long)];
  } u;
  u.l = 1;
  exit (u.c[sizeof (long) - 1] == 1);
}
$ 
$ /export/Plocal/GCC-3.3.6/gcc/xgcc -B/export/Plocal/GCC-3.3.6/gcc/
-B/usr/local/gcc-3.3.6/sparc-sun-solaris2.8/bin/
-B/usr/local/gcc-3.3.6/sparc-sun-solaris2.8/lib/ -isystem
/usr/local/gcc-3.3.6/sparc-sun-solaris2.8/include -c -O2 -g -O2  conftest.c
$ echo $?
0
$ 

As far as I can understand the original error message in config.log is:

[...]
configure: In function `main':
configure:3440: error: `bogus' undeclared (first use in this function)
configure:3440: error: (Each undeclared identifier is reported only once
configure:3440: error: for each function it appears in.)
configure:3440: error: syntax error before "endian"
[...]

and it applies to:

#include "confdefs.h"
#include <sys/types.h>
#include <sys/param.h>
int main() {

#if !BYTE_ORDER || !BIG_ENDIAN || !LITTLE_ENDIAN
 bogus endian macros
#endif
; return 0; }

In the first test, the one that fails, none of BYTE_ORDER, BIG_ENDIAN or
LITTLE_ENDIAN are defined. The configure script then runs a second test which
doesn't fail as shown above. Somehow the configure script takes into account the
first failure.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21782


  parent reply	other threads:[~2005-05-30  7:51 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 [this message]
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
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=20050530075104.609.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).