From: tomas@fabula.de
Cc: guile-devel@gnu.org
Subject: Re: autconf stdint types checking in guile-core
Date: Wed, 16 Apr 2003 10:59:32 +0200 [thread overview]
Message-ID: <20030416085932.GA17905@www> (raw)
In-Reply-To: <Pine.BSF.4.51.0304160304010.90801@helena.whitefang.com>
On Wed, Apr 16, 2003 at 03:28:21AM -0400, Thamer Al-Harbash wrote:
> On Wed, 16 Apr 2003, Rob Browning wrote:
>
> > Actually, this may be hard to get right. I haven't yet figured out a
> > way to get the value of CHAR_BIT either at configure time, or from the
> > C compiler at gen-scmconfig time in the cross-compilation case...
>
> Is AC_TRY_RUN at configure time bad for cross compilation? I'm
> assuming it is.
It is. You *get* the characteristics of the machine you are compiling
on [1]. You *want* the characteristics of the machine your compiled stuff
is supposed to be run.
There is no simple solution to this problem, IMHO, short of...
say building a `probe' program you send to the target machine
to collect characteristics and `bring them back' to the compilation
host.
Does auto-* have such a thing?
-------
[1] To be more precise ...the machine you are running configure on.
Regards
-- tomas
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-04-16 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 19:01 autconf stdint types checking in guile-core Thamer Al-Harbash
2003-04-16 5:54 ` Rob Browning
2003-04-16 6:16 ` Rob Browning
2003-04-16 7:28 ` Thamer Al-Harbash
2003-04-16 8:59 ` tomas [this message]
2003-04-16 12:11 ` Marius Vollmer
2003-04-16 16:22 ` Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030416085932.GA17905@www \
--to=tomas@fabula.de \
--cc=guile-devel@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).