Re: distcheck does not set exec_prefix - bug? distcheck fails for packages using e.g. pkglibdir

2007-10-16 Thread Ralf Wildenhues
Hello Daniel, * Daniel Leidert wrote on Wed, Oct 17, 2007 at 03:02:33AM CEST: > > Hm. After removing the small snippet from configure.ac setting > exec_prefix to "/usr/local" if its value is "NONE" (IIRC I added it, > because it was necessary to fix its value), everything works and > exec_prefix

Re: distcheck does not set exec_prefix - bug? distcheck fails for packages using e.g. pkglibdir

2007-10-16 Thread Daniel Leidert
Am Mittwoch, den 17.10.2007, 02:41 +0200 schrieb Daniel Leidert: > Hi, > > Today I observed an issue when I tried to run `make distcheck' as usual > for one of the project I'm contributing to. The issue was, that > distcheck failed at the step of installing a library. It told me, that > it was not

distcheck does not set exec_prefix - bug? distcheck fails for packages using e.g. pkglibdir

2007-10-16 Thread Daniel Leidert
Hi, Today I observed an issue when I tried to run `make distcheck' as usual for one of the project I'm contributing to. The issue was, that distcheck failed at the step of installing a library. It told me, that it was not able to remove the library from /usr/local/lib/$package Of course I tried

Re: xxx_LIBRARIES does ranlib on install

2007-10-16 Thread NightStrike
On 10/16/07, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > On Tue, 16 Oct 2007, NightStrike wrote: > > > If I place something inside the primary "_LIBRARIES", for instance > > libmine.a, when I do a make install after doing a make, make runs > > ranlib on that library. Why is ranlib run during make

Re: xxx_LIBRARIES does ranlib on install

2007-10-16 Thread NightStrike
On 10/16/07, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > On Tue, 16 Oct 2007, NightStrike wrote: > > Regarding your question about executable DLLs, if you take a look in > your Windows System directory you will see that DLLs are marked as > executable. Traditionally DLLs are found using the execu

Re: xxx_LIBRARIES does ranlib on install

2007-10-16 Thread Bob Friesenhahn
On Tue, 16 Oct 2007, NightStrike wrote: If I place something inside the primary "_LIBRARIES", for instance libmine.a, when I do a make install after doing a make, make runs ranlib on that library. Why is ranlib run during make install instead of during make all? Many systems supporting ranlib

Makefile.am assistance

2007-10-16 Thread NightStrike
I am trying to build a Makefile.am file "correctly". This is what I have so far: http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/experimental/buildsystem/Makefile.am?revision=137&view=markup Some issues that I've noted include installing all libraries as executables instead of 644 (due to

xxx_LIBRARIES does ranlib on install

2007-10-16 Thread NightStrike
If I place something inside the primary "_LIBRARIES", for instance libmine.a, when I do a make install after doing a make, make runs ranlib on that library. Why is ranlib run during make install instead of during make all?

Re: $(COMPILE)

2007-10-16 Thread NightStrike
On 10/16/07, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > On Tue, 16 Oct 2007, NightStrike wrote: > > > Where is $(COMPILE) documented? When should it be used? What does it > > actually get set to? > > Read a generated Makefile and all secrets will be revealed. Looks like here's my answer: COMP

Re: Specify location for noinst_PROGRAMS

2007-10-16 Thread myrdos2
Yes, that did the trick. Thanks! -- View this message in context: http://www.nabble.com/Specify-location-for-noinst_PROGRAMS-tf4623107.html#a13237339 Sent from the Gnu - Automake - General mailing list archive at Nabble.com.

Re: $(COMPILE)

2007-10-16 Thread NightStrike
On 10/16/07, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: > On Tue, 16 Oct 2007, NightStrike wrote: > > > Where is $(COMPILE) documented? When should it be used? What does it > > actually get set to? > > Read a generated Makefile and all secrets will be revealed. Normally > you should not care abo

Re: $(COMPILE)

2007-10-16 Thread Bob Friesenhahn
On Tue, 16 Oct 2007, NightStrike wrote: Where is $(COMPILE) documented? When should it be used? What does it actually get set to? Read a generated Makefile and all secrets will be revealed. Normally you should not care about $(COMPILE) since Automake takes care of it. Bob ===

Re: Changing $libdir

2007-10-16 Thread Bob Friesenhahn
On Tue, 16 Oct 2007, NightStrike wrote: If I do: lib_LIBRARIES = libfoo.a libfoo_a_SOURCES = foo.c in the Makefile.am, libfoo.a will be installed into $(prefix)/lib. If I am using AC_CANONICAL_SYSTEM in configure.ac, I want to be able to set build, host, and target for building a cross compil

Re: $(COMPILE)

2007-10-16 Thread NightStrike
On 10/16/07, Benoit SIGOURE <[EMAIL PROTECTED]> wrote: > On Oct 16, 2007, at 10:05 AM, NightStrike wrote: > > > Where is $(COMPILE) documented? > > http://www.gnu.org/software/automake/manual/html_node/Program- > variables.html#index-COMPILE-494 > > > When should it be used? > > When you want to "c

Re: $(COMPILE)

2007-10-16 Thread Benoit SIGOURE
On Oct 16, 2007, at 10:05 AM, NightStrike wrote: Where is $(COMPILE) documented? http://www.gnu.org/software/automake/manual/html_node/Program- variables.html#index-COMPILE-494 When should it be used? When you want to "compile a C source file" (quoting the manual). Maybe this works fo

Re: Changing $libdir

2007-10-16 Thread Benoit SIGOURE
On Oct 16, 2007, at 9:31 AM, NightStrike wrote: If I do: lib_LIBRARIES = libfoo.a libfoo_a_SOURCES = foo.c in the Makefile.am, libfoo.a will be installed into $(prefix)/lib. If I am using AC_CANONICAL_SYSTEM in configure.ac, I want to be able to set build, host, and target for building a cros

$(COMPILE)

2007-10-16 Thread NightStrike
Where is $(COMPILE) documented? When should it be used? What does it actually get set to?

Changing $libdir

2007-10-16 Thread NightStrike
If I do: lib_LIBRARIES = libfoo.a libfoo_a_SOURCES = foo.c in the Makefile.am, libfoo.a will be installed into $(prefix)/lib. If I am using AC_CANONICAL_SYSTEM in configure.ac, I want to be able to set build, host, and target for building a cross compiler. I would then want the above library to