From: Kalle Olavi Niemitalo <email@example.com>
Subject: Makefile preprocessing trouble (was %load-path)
Date: Sun, 09 Apr 2000 12:46:00 -0000 [thread overview]
Message-ID: <87hfdb83cq.fsf@PC486.Niemitalo.LAN> (raw)
I have implemented points 1-4 of my %load-path plan at home.
However, I haven't been able to test the code because I hit some
trouble with GUILE_LDFLAGS. I have the Guile libraries at
/home/kalle/i386-pc-linux-gnu/lib/, and when that goes through
the C preprocessor (which Emacs uses for some makefiles), the
"i386" turns to " 1 " which the linker doesn't like at all.
It seems Emacs has had this problem before (with other
variables), and configure.in contains code to add -U options on
the preprocessor command line to get rid of predefined symbols.
(Search for "the horror".) I tried adding $GUILE_CFLAGS and
$GUILE_LDFLAGS in the list of protected variables, but that
didn't work out because the commands are run in config.status and
the variables are not defined there.
Any suggestions how to tackle this problem?
next prev parent reply other threads:[~2000-04-09 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-26 8:45 automating %load-path Kalle Olavi Niemitalo
2000-03-26 10:51 ` Keisuke Nishida
2000-03-27 9:08 ` Kalle Olavi Niemitalo
2000-03-27 17:28 ` Keisuke Nishida
2000-03-29 2:33 ` before the 0.3 release (was %load-path) Kalle Olavi Niemitalo
2000-04-09 12:46 ` Kalle Olavi Niemitalo [this message]
2000-04-10 3:47 ` Makefile preprocessing trouble " Kalle Olavi Niemitalo
2000-04-14 0:29 ` automating %load-path Kalle Olavi Niemitalo
2000-04-29 1:21 ` Kalle Olavi Niemitalo
2000-04-29 1:46 ` Keisuke Nishida
2000-04-29 11:37 ` Kalle Olavi Niemitalo
2000-04-29 12:27 ` Keisuke Nishida
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).