From: Joe deBlaquiere <jadb@redhat.com>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
"MIPS/Linux List (SGI)" <linux-mips@oss.sgi.com>
Subject: Re: Dumb Question on Cross-Development
Date: Sat, 07 Apr 2001 10:29:01 -0500 [thread overview]
Message-ID: <3ACF323D.3030704@redhat.com> (raw)
In-Reply-To: Pine.GSO.3.96.1010404153012.6521E-100000@delta.ds2.pg.gda.pl
Maciej W. Rozycki wrote:
> On Wed, 4 Apr 2001, Ralf Baechle wrote:
>
>
>> stdint.h isn't available everywhere. Aside of that I won't object ...
>
>
> That's why I wrote of legacy hosts. The AC_CHECK_HEADERS and
> AC_CHECK_TYPE macros are cross-compilation-safe and they are all that
> modern hosts need. For other hosts AC_CHECK_SIZEOF might be used to find
> generic types suitable for ISO C definitions, which might be problematic
> for cross-compilation, though. Still this applies to non-gcc
> cross-compilers only, which are not that common, AFAIK.
You might call it a hack, but it makes life easy if you do something like:
export ac_cv_sizeof_short=2
export ac_cv_sizeof_int=4
export ac_cv_sizeof_long=4
sh ./configure --target=$CONFIG_TARGET --host=$CONFIG_HOST
--prefix=$CONFIG_PREFIX --exec-prefix=$CONFIG_EXECPR
This will short circuit a "broken" configure trying to execute programs
for this kind of thing. If configure doesn't care about sizeof_int, then
this definition is silently ignored...
--
Joe deBlaquiere
Red Hat, Inc.
307 Wynn Drive
Huntsville AL, 35805
voice : (256)-704-9200
fax : (256)-837-3839
next prev parent reply other threads:[~2001-04-07 16:24 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 12:24 Dumb Question on Cross-Development Kevin D. Kissell
2001-04-02 12:24 ` Kevin D. Kissell
2001-04-02 13:14 ` Ralf Baechle
2001-04-02 13:14 ` Ralf Baechle
2001-04-02 19:20 ` Kevin D. Kissell
2001-04-02 19:20 ` Kevin D. Kissell
2001-04-02 21:48 ` Florian Lohoff
2001-04-02 22:22 ` Kevin D. Kissell
2001-04-02 22:22 ` Kevin D. Kissell
2001-04-02 22:30 ` Florian Lohoff
2001-04-03 2:57 ` Joe deBlaquiere
2001-04-04 15:17 ` Jay Carlson
2001-04-04 15:17 ` Jay Carlson
2001-04-03 6:11 ` Geert Uytterhoeven
2001-04-03 9:52 ` Maciej W. Rozycki
2001-04-03 9:50 ` Maciej W. Rozycki
2001-04-03 17:34 ` Jun Sun
2001-04-04 10:02 ` Florian Lohoff
2001-04-04 10:15 ` Geert Uytterhoeven
2001-04-04 11:02 ` Florian Lohoff
2001-04-04 12:15 ` Maciej W. Rozycki
2001-04-04 11:22 ` Alan Cox
2001-04-04 11:22 ` Alan Cox
2001-04-04 16:05 ` Florian Lohoff
2001-04-04 18:06 ` Jun Sun
2001-04-04 18:45 ` Florian Lohoff
2001-04-06 9:37 ` Wichert Akkerman
2001-04-03 9:26 ` Maciej W. Rozycki
2001-04-03 15:10 ` Ralf Baechle
2001-04-04 12:06 ` Maciej W. Rozycki
2001-04-04 12:29 ` Ralf Baechle
2001-04-04 13:39 ` Maciej W. Rozycki
2001-04-04 14:23 ` Carsten Langgaard
2001-04-04 15:37 ` Maciej W. Rozycki
2001-04-05 10:54 ` Carsten Langgaard
2001-04-05 12:05 ` Maciej W. Rozycki
2001-04-05 14:35 ` Carsten Langgaard
2001-04-05 16:50 ` Maciej W. Rozycki
2001-04-05 12:32 ` Ralf Baechle
2001-04-06 15:30 ` Maciej W. Rozycki
2001-04-07 15:29 ` Joe deBlaquiere [this message]
2001-04-09 12:16 ` Maciej W. Rozycki
2001-04-02 21:56 ` Thiemo Seufer
2001-04-02 23:41 ` Binutils fixed to deal with 'insmod' issue and discussion Steven J. Hill
2001-04-03 2:17 ` Thiemo Seufer
2001-04-03 8:26 ` Ralf Baechle
2001-04-03 17:27 ` Steven J. Hill
2001-04-04 5:57 ` Andreas Jaeger
2001-04-04 16:12 ` Thiemo Seufer
2001-04-03 15:46 ` Steven J. Hill
2001-04-03 16:59 ` Maciej W. Rozycki
2001-04-03 16:56 ` Steven J. Hill
2001-04-04 11:35 ` Maciej W. Rozycki
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=3ACF323D.3030704@redhat.com \
--to=jadb@redhat.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.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