From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: AARRRRGGH! Die Libtool, die!
Date: Sun, 16 Feb 2003 00:54:18 +0100 [thread overview]
Message-ID: <15950.54058.520676.489870@blauw.xs4all.nl> (raw)
In-Reply-To: <87smupi86u.fsf@raven.i.defaultvalue.org>
rlb@defaultvalue.org writes:
> Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
>
> > WTF is it recompiling stuff during installation?
>
> I'm not particularly fond of that "feature" either. I think it has to
> do with trying to have libs that will work from the install tree vs
> libs that will work from the build tree. (i.e. perhaps different
> -rpaths, etc., and it may be aggravated by cross-platform issues).
>
> If you haven't done it already, I'd try a "make distclean" and
> (re)running ./autogen.sh and see if that helps. If not, we'll try
> something else.
Ah, distclean. I only did "make clean". Thanks, it seems to work now.
> (Personally, I'd rather have all those tools (auto* included) written
> in something like perl -- it's nearly as ubiquitous and *far* more
> managable. Of course perl couldn't use them then, but AFAIK, it
> doesn't anyway.)
I would use Python myself, but otherwise I concur.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-02-15 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 14:36 AARRRRGGH! Die Libtool, die! Han-Wen Nienhuys
2003-02-15 20:46 ` Rob Browning
2003-02-15 23:54 ` Han-Wen Nienhuys [this message]
2003-02-16 0:56 ` Tom Lord
2003-02-18 11:24 ` tomas
2003-02-18 17:14 ` Rob Browning
2003-02-18 18:50 ` rm
2003-02-19 13:04 ` tomas
2003-02-21 17:28 ` Rob Browning
2003-02-16 1:09 ` Rob Browning
-- strict thread matches above, loose matches on Subject: below --
2003-02-15 14:26 Han-Wen Nienhuys
2003-02-18 11:04 ` tomas
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=15950.54058.520676.489870@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--cc=guile-devel@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).