Re: Iperf build break with emake.

I've used emake and always get this error irrespective of package. Ofcourse, this happens only when something changes and automake decides to recreate configure and then rerun it. All I've been able to trace is that emake (probably) runs the configure script on one of its agents and that creates t

Makefile.in's in build tree

Hi, I maintain my build tree separate to src tree which has all the Makefile.am's. Is it possible that all generated files (including the Makefile.in's and the various cache) be in the build tree ? kamaljit

remove dependency on Makefile.am in Makefile.in

I was wondering if the following is plausible -- I use Makefile.am and run automake (autoreconf, really) to create the Makefile.in's When I distribute the project, I dont want to distribute configure.ac and Makefile.am, rather distribute only the generated configure and Makefile.in's. Is this pos

Re: using install.sh selectively

re ? kamaljit Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hello Kamaljit, * Kamaljit Singh wrote on Fri, Jan 11, 2008 at 12:25:48AM CET: > > I am trying to use "make install-strip" and that tries to strip all > _PROGRAMS. But I dont want all the PROGRAMS that I build shoul

Re: Building automake1.9 with autoconf2.61

genuine quandary ... kamaljit Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hello Kamaljit, * Kamaljit Singh wrote on Fri, Jan 25, 2008 at 01:00:52AM CET: > > Moreover automake1.9 is dependent on autoconf2.58+ to be present in > the path that I cant have them in the same sandbox at all

Re: Building automake1.9 with autoconf2.61

r than use AC_CONFIG_SUBDIRS(). Currently, I am using a script, but I think AC_CONFIG_SUBDIRS() is much more powerful as I dont need to maintain any scripts anymore and I could just write a configure.ac and for most part its no or low maintenance. kamaljit Bob Proulx <[EMAIL PROTECTED]> wrote: Kama

Building automake1.9 with autoconf2.61

Hi, I was hoping to create a src tree which would build automake1.9 and autoconf2.61 and install them in a central place. Writing a configure.ac for this is quite hard if not impossible. The automake expects and depends on that the directory where its untarred should be called automake-1.9, which

Re: using install.sh selectively

break permanently, or was that a snide remark ? If the latter then I will use this preferably. Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Hello Kamaljit, * Kamaljit Singh wrote on Fri, Jan 11, 2008 at 12:25:48AM CET: > > I am trying to use "make install-strip" and t

using install.sh selectively

I am using automake 1.9. I am trying to use "make install-strip" and that tries to strip all _PROGRAMS. But I dont want all the PROGRAMS that I build should be stripped. Is there some out of the box way to do that ? I tried setting installPROGRAMS_INSTALL to $(INSTALL_DATA) but then automake error

Re: problem using the .a libs ...

The way the .a work is that if a undefined symbol is defined by a .o in the .a then only the .o is linked in otherwise it isnt linked in. But when you do *.o then you link in all .o's regardless. The .o's in the .a are evaluated as they are seen hence they'll not be revisited in case a later

How best to incorporate -Wl,--whole-archives with _PROGRAMS

I am trying to build a .so (without libtool) but instead using the _PROGRAMS. If I want to use -Wl,--whole-archives ... -Wl,--no-whole-archives in the _LDLIBS it barfs and if I use it in _LDFLAGS then it doesnt get into the dependencies, unless I explicitly put it. Any ideas on a better mechanism

Re: Custom Build

> $@; ... kamaljit Eric Blake <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Kamaljit Singh on 10/26/2007 4:17 PM: > Hi All, > > Is it possible to create custom build targets and dependencies quite like the > one for say C++ ? > For instance - &