From: Thamer Al-Harbash <tmh@whitefang.com>
Subject: Re: autconf stdint types checking in guile-core
Date: Wed, 16 Apr 2003 03:28:21 -0400 (EDT) [thread overview]
Message-ID: <Pine.BSF.4.51.0304160304010.90801@helena.whitefang.com> (raw)
In-Reply-To: <87k7dvc6hn.fsf@raven.i.defaultvalue.org>
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. Otherwise, AC_TRY_RUN a program that includes
limits.h, outputs the number of bits to a temporary file, read it
in and then make sure to put that temporary file in CLEANFILES in
the Makefile.am If CHAR_BITS is not defined put -1 in the file
meaning undefined.
The only other way is to use the preprocessor. I'm fairly certain
using -dM won't be portable everywhere though :|
char_bits=echo "#include <limits.h>" | cpp -dM | awk '/#define.*CHAR_BIT/ { pintf("%s", $3);}'
Using the preprocessor is more friendly to cross compilation
since we'd be, technically, be preprocessing the target hosts
header files.
--
Thamer Al-Harbash http://www.whitefang.com/
(if (> pressure too-much-pressure)
'flame 'work)
_______________________________________________
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 7:28 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 [this message]
2003-04-16 8:59 ` tomas
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=Pine.BSF.4.51.0304160304010.90801@helena.whitefang.com \
--to=tmh@whitefang.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).