Re: Modifying installed script names ?

2002-12-21 Thread John Levon
On Fri, Dec 13, 2002 at 12:30:32PM +0100, Alexandre Duret-Lutz wrote: > You could declare everybody using `noinst_SCRIPTS', and install > them using a custom `install-exec-local' rule. Thanks. I did : noinst_SCRIPTS = $(OP_START) $(OP_STOP) $(OP_DUMP) ... install-exec-local: $(INSTALL_

Passing configure options to make distcheck

2002-12-12 Thread John Levon
We have some code that is built by default, but cannot be successfully used with separate srcdir/objdir. However, a configure option can be used that doesn't need this code. make distcheck fails by default, but if I could pass in a configure option, it would work. Can I do this ? I'm using auto

Modifying installed script names ?

2002-12-12 Thread John Levon
Hi, we have three scripts that need to be installed differently depending on an configure option. If a condition is set, then op_start_25,op_dump_25,op_stop_25 need to be installed as op_start,op_dump,op_stop, otherwise we can just install the existing op_start/dump/stop in the source tree. How

Re: Linking in C++ mode

2002-11-14 Thread John Levon
On Thu, Nov 14, 2002 at 12:40:29PM +0100, Alexandre Duret-Lutz wrote: > You can override the LINK command on a per-program basis: > > foo_LINK = $(CXX) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ Works a treat. Thanks a lot. regards john -- Khendon's Law: If the same point is made t

Re: Linking in C++ mode

2002-11-10 Thread John Levon
On Mon, Nov 11, 2002 at 05:36:57AM +0100, Ralf Corsepius wrote: > 1. Finding a way to compile your program (independently of automake). > > You are using a library written in c++, therefore a general solution is > using "g++" to _link_ your program, even if your "main" is written in C. > > Rule

Re: Linking in C++ mode

2002-11-10 Thread John Levon
On Sun, Nov 10, 2002 at 10:39:59PM -0500, Pierre Sarrazin wrote: > By the way, to avoid having the 'dist' target include dummy.cc in > the distributed source tarball, one has to say this: whoops, forgot about this. thanks. > And to have 'clean' erase the generated dummy.cc: > > clean-local: >

Re: Linking in C++ mode

2002-11-10 Thread John Levon
On Sun, Nov 10, 2002 at 05:42:30PM -0500, Pierre Sarrazin wrote: > Another way to force automake to use g++ to link the application > seems to be to leave the .c alone, but to add a dummy.cc file to > the application's _SOURCES variable. The .c file is still compiled > by gcc. This seems like th

Re: Linking in C++ mode

2002-11-10 Thread John Levon
On Sun, Nov 10, 2002 at 06:50:47PM -0500, Earnie Boyd wrote: > >I do not think getting gcc to link -lstdc++ is a good idea either, but > >it doesn't have much more hack value than the solution you propose below > >IMHO. > > It's the hack that using g++ performs. I do not believe there is any gua

Re: Linking in C++ mode

2002-11-10 Thread John Levon
On Sun, Nov 10, 2002 at 01:01:08PM +0100, Ralf Corsepius wrote: > > You could always just add -lstdc++ to the oprofiled_LDADD variable. > This would be a fault, IMO. I do not think getting gcc to link -lstdc++ is a good idea either, but it doesn't have much more hack value than the solution you p

Linking in C++ mode

2002-11-09 Thread John Levon
We have a C program which links to a C++ library, and we need to tell automake to do the link in C++ mode to avoid undefined references to the C++ standard library. How can we do it ? The Makefile.am looks as follows : ---snip--- dist_sources = oprofiled.c opd_stats.c opd_kernel.c opd_image.c o

Re: spam

2002-05-14 Thread John Levon
On Tue, May 14, 2002 at 03:54:52PM -0700, Dan Kegel wrote: > IMHO the mailing list should reject messages from nonsubscribers. > I thought it already did. Every project considering doing this needs to ask themselves whether they are prepared to miss out on bug reports as a result. This is a fact