From: Jones Desougi <jones@ingate.com>
To: zack@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: AC_COMPILE_CHECK_SIZEOF
Date: Sun, 05 Sep 2004 23:45:00 -0000 [thread overview]
Message-ID: <200409052345.i85NjkDn004749@usagi.ingate.se> (raw)
In-Reply-To: <87brgk4pgs.fsf@codesourcery.com> (message from Zack Weinberg on Sun, 05 Sep 2004 10:04:19 -0700)
> For mainline, I think it would be better if you cut us over to
> plain AC_CHECK_SIZEOF, which works correctly when cross-compiling in
> autoconf 2.5x.
That isn't a simple one line fix though. :-)
A brief glance suggests that it may not be that much more, but that
there are subtle differences in behaviour.
Interestingly enough, libjava and fastjar appears to have moved in the
other direction in 2002, for the latter as part of cross-compiling support.
How about starting off with the simple patch to fix the broken macro?
> For 3.4, we'd need to know that there was an actual problem before
> changing anything. Did you encounter a problem?
There should be no bad effects of this bug for current 3.4.
/Jones
next prev parent reply other threads:[~2004-09-05 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 15:45 AC_COMPILE_CHECK_SIZEOF Jones Desougi
2004-09-05 17:04 ` AC_COMPILE_CHECK_SIZEOF Zack Weinberg
2004-09-05 23:45 ` Jones Desougi [this message]
2004-09-06 0:44 ` AC_COMPILE_CHECK_SIZEOF Zack Weinberg
2004-09-06 14:36 ` AC_COMPILE_CHECK_SIZEOF Giovanni Bajo
2004-09-06 16:44 ` AC_COMPILE_CHECK_SIZEOF Zack Weinberg
2004-09-06 22:03 ` AC_COMPILE_CHECK_SIZEOF Jones Desougi
2004-09-07 4:56 ` AC_COMPILE_CHECK_SIZEOF Zack Weinberg
2004-09-13 13:18 ` AC_COMPILE_CHECK_SIZEOF Jones Desougi
2004-09-13 21:13 ` AC_COMPILE_CHECK_SIZEOF Zack Weinberg
2004-09-13 21:20 ` AC_COMPILE_CHECK_SIZEOF DJ Delorie
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=200409052345.i85NjkDn004749@usagi.ingate.se \
--to=jones@ingate.com \
--cc=gcc@gcc.gnu.org \
--cc=zack@codesourcery.com \
/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).