unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: cvs libguile-ltdl and scmconfig.h
Date: Thu, 13 Mar 2003 09:16:11 +1000	[thread overview]
Message-ID: <873clsdvlw.fsf@zip.com.au> (raw)

Now that libguile/scmconfig.h is a generated file, I think
libguile-ltdl needs to express that it should be built before
attempting to compile libguile-ltdl.la.

Without that, raw-ltdl.c can hit /usr/include/libguile/scmconfig.h,
which is likely to be wrong (in my case the debian packaged guile
1.4).

I got some joy from adding the following to libguile-ltdl/Makefile.am

	BUILT_SOURCES = ../libguile/scmconfig.h
	../libguile/scmconfig.h:
	        cd ../libguile; $(MAKE) $(AM_MAKEFLAGS) scmconfig.h

Or alternately maybe raw-ltdl.c only really needs config.h now.  I'm
not smart enough to tell.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2003-03-12 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 23:16 Kevin Ryde [this message]
2003-03-13  0:33 ` cvs libguile-ltdl and scmconfig.h 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=873clsdvlw.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).