libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building CVS HEAD libtool outside of source directory


From: Gary V. Vaughan
Subject: Re: Building CVS HEAD libtool outside of source directory
Date: Fri, 19 Oct 2007 17:47:30 +0100

Hi Bob,

On 19 Oct 2007, at 16:18, Bob Friesenhahn wrote:
On Fri, 19 Oct 2007, Gary V. Vaughan wrote:

All of my builds are done with VPATH, and I use the commit script with them just fine!

When bootstrap completes it says this:

WARNING: You might want to regenerate `commit' and `libltdl/config/ mailnotify' WARNING: after you have run `configure' to discover the real whereabouts
WARNING: of `sed', `grep' etc. like this:
WARNING:
WARNING:      rm -f commit libltdl/config/mailnotify
WARNING: make -f Makefile.maint ./commit ./libltdl/config/ mailnotify

Please explain how this is addressed in the context of a VPATH build where only bootstrap is executed in the source tree.

The default build uses plain 'sed, grep etc' with path lookups even though configure may discover alternatives (gsed, ggrep for instance) that it prefers. If plain sed or grep are seriously brain damaged, then there is a chance that things will go haywire.

I expect that the commit script will work by default on your system since you are the one who wrote it. :-)

% gmake -n -f Makefile.maint ./commit ./libltdl/config/mailnotify
Makefile.maint:27: Makefile: No such file or directory
 *** Run maintainer rules from the build tree, with
 *** `make -f../Makefile.maint' for example, where
 *** `../' is the relative path back to the directory
 *** that contains the `Makefile.maint'.  Alternatively,
 *** run `./configure' in the source tree for an in
 *** tree build.
gmake: *** [Makefile] Error 1

However, then I follow these instructions I see the warning
../../../../home/bfriesen/src/gnu/libtool-head/Makefile.maint:29: warning: overriding commands for target `Makefile'
Makefile:692: warning: ignoring old commands for target `Makefile'

and nothing gets done.

Bah. What is the relative path back to your source directory? I'll try to reproduce next time I am hacking on libtool...

I know that the answer would be intuitively obvious if I drank some Guinness beer (works like spinach does for Popeye) but it is morning here, and in the US we don't start as early as you folks do.

Well, more like icepops to earthworm Jim... ;-)

Cheers,
        Gary
--
  ())_.              Email me: address@hidden
  ( '/           Read my blog: http://blog.azazil.net
  / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_ Join my AGLOCO Network: http://www.agloco.com/r/BBBS7912




Attachment: PGP.sig
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]