From: "Andreas Vögele" <voegelas@gmx.net>
Subject: building gen-scmconfig.c on FreeBSD
Date: Wed, 8 Sep 2004 08:22:29 +0200 [thread overview]
Message-ID: <75F4554A-015F-11D9-A50A-000D93673682@gmx.net> (raw)
On FreeBSD string.h includes the system header strings.h. The problem
is that Guile provides another file called strings.h which is included
instead of the system header file. This causes the build of
gen-scmconfig to fail since Guile's strings.h includes scmconfig.h
which hasn't been created at this stage.
It seems that there is already a workaround for this problem in
linguile/Makefile.am:
## Prevent automake from adding extra -I options
DEFS = @DEFS@
Unfortunately, that workaround no longer helps since recent versions of
automake seem to work differently. I tried to use "DEFS = @DEFS@
-I/usr/include" so that /usr/include is searched before the
DEFAULT_INCLUDES. But that didn't work since GCC seems to search the
current directory before the directories added with -I. I also tried to
use -I- without success.
I figured out that gen-scmconfig can be built with CC_FOR_BUILD instead
of COMPILE. I'm wondering if the rule
gen-scmconfig.$(OBJEXT): gen-scmconfig.c
if [ "$(cross_compiling)" = "yes" ]; then \
$(CC_FOR_BUILD) $(DEFS) $(INCLUDES) -c -o $@ $<; \
else \
$(COMPILE) -c -o $@ $<; \
fi
in libguile/Makefile.am couldn't be replaced with
gen-scmconfig.$(OBJEXT): gen-scmconfig.c
$(CC_FOR_BUILD) $(DEFS) $(INCLUDES) -c -o $@ $<;
Does anybody know a better solution?
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2004-09-08 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 6:22 Andreas Vögele [this message]
2004-09-08 22:26 ` building gen-scmconfig.c on FreeBSD Kevin Ryde
2004-09-14 19:18 ` Rob Browning
2004-09-15 22:19 ` Kevin Ryde
2004-09-16 5:28 ` 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=75F4554A-015F-11D9-A50A-000D93673682@gmx.net \
--to=voegelas@gmx.net \
/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).