Re: [avr-libc-dev] Re: circ dep fix

[Theodore Roth]

On Mon, 5 Aug 2002, Joerg Wunsch wrote:

:) > There's nothing to fix. Just don't use the do* scripts.
:)
:) Well, i think that's more a misfeature of automake, see the followup to
:) my own mail.  It places empty DESTDIR= macros in each and everey
:) generated Makefile.in.  I don't think using another method than the do*
:) scripts would change the behaviour, and in fact
:)
:) ../domake DESTDIR=/tmp install
:)
:) did work for me (domake passes all its arguments down to the make
:) utility).

Ah, this works because of the way make deals with env variable. Let's say
you have a makefile fragment like this:

  DESTDIR =

Doing this:

  $ DESTDIR=foo make install

will not cause make to override DESTDIR. You force the overide with a '-e'
in gmake though. Now, what you did above, ends up like this:

  $ make DESTDIR=foo install

This time make overrides the empty DESTDIR with what is on the command
line. This _way_ safer than using '-e' since '-e' would override all
variable that exist in the environment. Of course, I'm talking about gmake
here, as I don't know anything about bsd make.

BTW: the do* scripts are not part of autoconf/automake. They are just
convience scripts that Reinhard added.

:)
:) > I personally only
:) > use the reconf script, then manually run configure as such (from obj-avr
:) > subdir):
:) >
:) >   $ cd obj-avr; ../configure --prefix=$HOME/local/libc-test
:)
:) Hmm.  However, --prefix is something different than DESTDIR.  DESTDIR
:) is used to modify the entire root of the installation target.  So you
:) configure it as normal, e. g. with --prefix=/usr/local (the default),
:) compile it, but when it comes to installation, you say DESTDIR=/foo,
:) and it will install it all into /foo/usr/local.

Once again you've exposed my ignorance. ;-)

By all means, what you want to do should be made to work. I just didn't
realize that's what DESTDIR is doing. That would make my life easier too.
;-)

Ted Roth