From: Alan Modra <amodra@bigpond.net.au>
To: Rainer Emrich <rainer@emrich-ebersheim.de>
Cc: binutils@sourceware.org
Subject: Re: bfdlibdir and bfdincludedir change
Date: Wed, 26 Aug 2009 07:25:00 -0000 [thread overview]
Message-ID: <20090826071947.GN17804@bubble.grove.modra.org> (raw)
In-Reply-To: <4A93D50C.4070404@emrich-ebersheim.de>
On Tue, Aug 25, 2009 at 02:11:56PM +0200, Rainer Emrich wrote:
> That sounds reasonable. But why are the directories created even if libbfd is
> not install at all?
We used to not create the directories, but Ralf deleted our custom
install rules when converting to the latest autotools. Seems like the
standard automake rules always create the dirs.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2009-08-26 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 17:51 Rainer Emrich
2009-08-25 1:50 ` Alan Modra
2009-08-25 12:23 ` Rainer Emrich
2009-08-26 7:25 ` Alan Modra [this message]
2009-08-26 19:58 ` Ralf Wildenhues
2009-08-27 6:42 ` Alan Modra
2009-10-11 11:36 ` Allow variable override of, rather than by, silent variables. (was: bfdlibdir and bfdincludedir change) Ralf Wildenhues
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090826071947.GN17804@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
--cc=rainer@emrich-ebersheim.de \
/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).