From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: building gen-scmconfig.c on FreeBSD
Date: Thu, 09 Sep 2004 08:26:24 +1000 [thread overview]
Message-ID: <87sm9s5re7.fsf@zip.com.au> (raw)
In-Reply-To: <75F4554A-015F-11D9-A50A-000D93673682@gmx.net> (Andreas Vögele's message of "Wed, 8 Sep 2004 08:22:29 +0200")
Andreas Vögele <voegelas@gmx.net> writes:
>
> gen-scmconfig.$(OBJEXT): gen-scmconfig.c
> $(CC_FOR_BUILD) $(DEFS) $(INCLUDES) -c -o $@ $<;
Yep, I'd been meaning to do that. But probably omitting $INCLUDES,
since they're likely to be host-system things, not build-system.
$DEFS probably only has -DHAVE_CONFIG_H, and may be unnecessary too.
One thing for a proper cross-compile is to figure out
$OBJEXT_FOR_BUILD, which may be different from the host system. I'd
planned to go straight to an executable rather than through an obj.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-09-08 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 6:22 building gen-scmconfig.c on FreeBSD Andreas Vögele
2004-09-08 22:26 ` Kevin Ryde [this message]
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=87sm9s5re7.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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).