how to use AC_CHECK_LIB without LDFLAGS?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi folks, I am new to autoconf and automake, so please excuse if you heard this too often. My question is: How can I use AC_CHECK_LIB without setting a global LDFLAGS? Using automake I can specify linker flags per program, e.g. foo_LDFLAGS = -L/somepath

Re: how to use AC_CHECK_LIB without LDFLAGS?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Braden McDaniel wrote: | | I don't fully understand the problem you're describing; but perhaps you | want to do something like this: | | save_LDFLAGS="$LDFLAGS" | LDFLAGS="$LDFLAGS -Lwhatever" | AC_CHECK_LIB(...) | LDFLAGS="$save_LDFLAGS" | No, what I w

Re: how to use AC_CHECK_LIB without LDFLAGS?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Braden McDaniel wrote: | Harald Dunkel wrote: | |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA1 |> |> Braden McDaniel wrote: |> | |> | I don't fully understand the problem you're describing; but perhaps you |> |

CVS Access?

Hi folks, The GNU autoconf page says that the current version can be downloaded via CVS from :pserver:[EMAIL PROTECTED]:/cvsroot/autoconf But cvs got stuck when I tried. Is this still valid? If not, would somebody please post the new server? Many thanx Harri

Re: CVS Access?

Bob Proulx wrote: Hmm... No that doc is wrong. It should be this: :ext:[EMAIL PROTECTED]:/cvsroot/autoconf Found it. Many thanx Harri ___ Autoconf mailing list Autoconf@gnu.org http://lists.gnu.org/mailman/listinfo/autoconf

Re: how to set a default program-prefix whithin configure.ac

JRBCAST wrote: Hi all, First of all, sorry if you have received this mail two times. My question is: How can I set a default progra-prefix without the need to explicitely pass it whith: ./configure --program-prefix ... Look for AC_PREFIX_PROGRAM in the autoconf manual (4.12). Another question i

Re: can I use dmesg to detect CPU type?

[EMAIL PROTECTED] wrote: Hi, i'm a newbie, and i need to have my library optimized for the cpu installed in the system of the user. Can I use dmesg messages to do it? there is a better way? AC_CANONICAL_TARGET? Regards Harri ___ Autoconf mailing list Aut

lib_LIBRARIES must be set with `=' before using `+='

Hi folks, Automake gave me this message: mylib/Makefile.inc:19: lib_LIBRARIES must be set with `=' before using `+=' Makefile.am:5: `mylib/Makefile.inc' included from here I would not like to add any assumption to Makefile.inc whether lib_LIBRARIES has been set before. So I have added lib

Re: lib_LIBRARIES must be set with `=' before using `+='

Andre Caldas wrote: Hello, Harald! You can always make a brand new variable: defaultlibdir = $(libdir) defaultlib_LIBRARIES = . This is a nice idea. (I am still new to autoconf/ automake, so some constructs are not that obvious to me.) The libraries to be built are managed using canonical names

Re: autoconf macros, portable arithmetic

Paul Eggert wrote: Stepan Kasal <[EMAIL PROTECTED]> writes: Why not do something like this instead? This suffices for 4-part version numbers but it's easy to increase this. # Example inputs a=3.5.37 b=3.5.371 If you put some other values here, then you get 0.007 > 0.42 Regards Harri __

http://sources.redhat.com/ml/autoconf/

Hi folks, every time I google for autoconf mailing list I am cheated into http://sources.redhat.com/ml/autoconf/, even though there are just empty mailboxes since March 02. Would it be possible to either put a redirection there, or to add a note saying that the official mailing list archive is some

Re: how to avoid PACKAGE and VERSION?

Harald Dunkel wrote: Hi folks, How can I tell autoconf/automake to _not_ define macros for PACKAGE and VERSION? Found it: no-define. Thanx anyway Harri ___ Autoconf mailing list Autoconf@gnu.org http://lists.gnu.org/mailman/listinfo/autoconf

how to avoid PACKAGE and VERSION?

Hi folks, How can I tell autoconf/automake to _not_ define macros for PACKAGE and VERSION? VERSION conflicts with some 3rd party code in my case. Regards Harri ___ Autoconf mailing list Autoconf@gnu.org http://lists.gnu.org/mailman/listinfo/autoconf

Re: lib_LIBRARIES must be set with `=' before using `+='

Harald Dunkel wrote: This is my suggestion: --- ../old/automake-1.9.5/lib/Automake/VarDef.pm2004-09-21 20:20:34.0 +0200 +++ lib/Automake/VarDef.pm 2005-02-24 09:07:21.106214815 +0100 @@ -152,7 +152,7 @@ # A user variable must be set by either `=' or `:=',

question about the *.Po files

Hi folks, I noted that sometimes the *.Po file for a *.o file looks like this utils/src/libbigint_a-bigint.o : \ \ /local/tmp/nbuild/sandboxsLSPpw/src/utils/src/bigint.cc \ /usr/include/string.h /usr/include/features.h \ : : and sometimes like this sound.o sound.o: ../../../src/mylib/sound

Re: question about the *.Po files

Ralf Wildenhues wrote: > Hi Harald, > > * Harald Dunkel wrote on Wed, Apr 06, 2005 at 10:01:56AM CEST: > >> >>How comes? > > > Mostly compiler variations. Automake's `depcomp' script knows different > ways to invoke compilers, so they output dep

Re: x86_64 and x86 userland

Ralf Wildenhues wrote: > I have a question regarding systems with more than one ABI, specifically > x86_64. If you consider for example the Debian distribution which has a > x86_64 kernel, but a completely x86 userland, config.guess still gives > you x86_64-unknown-linux-gnu as output. (I have be

abs_top_builddir not working?

Hi folks, is it possible that abs_top_builddir and the other abs_* macros are not working? I tried to replace $(top_builddir) in a Makefile.am by $(abs_top_builddir), but the new Makefile did not define this macro. ??? Regards Harri ___ Autoconf m

Re: abs_top_builddir not working?

Stepan Kasal wrote: > Hello, > > On Mon, May 09, 2005 at 06:02:24PM +0200, Harald Dunkel wrote: > >>I tried to replace $(top_builddir) >>in a Makefile.am by $(abs_top_builddir), but the new >>Makefile did not define this macro. > > > Actually, this i

using target-specific variables?

Hi folks, How can I use target-specific variables in Makefiles generated by Automake? My Makefile.am says something like lib_LIBRARIES = libmylib.a libmylib_gcc3.a libmylib_a_SOURCES = foo.c bar.c libmylib_gcc3_a_SOURCES = $(libmylib_a_SOURCES) libmylib_gc

Re: using target-specific variables?

Ralf Wildenhues wrote: > Hi Harald, > > * Harald Dunkel wrote on Thu, May 12, 2005 at 10:45:40AM CEST: > >>How can I use target-specific variables in Makefiles >>generated by Automake? > > > In general, that is not possible. > For specific variables, like

Re: using target-specific variables?

Ralf Wildenhues wrote: > > I believe we are misunderstanding each other completely. > > Do you need more than one compiler simultaneously within one build tree? > If not: forget my answer. > If so: please explain why you would need this. > Then we can discuss further. > Yes, I have to build lib

Re: using target-specific variables?

Stepan Kasal wrote: > > well, this behaviour is documented in the Automake manual, > in node ``Extending'': > > :Note that Automake does not make any difference between rules with > : commands and rules that only specify dependencies. So it is not > : possible to append new dependencies to a

calling AC_CANONICAL_HOST twice?

Hi folks, Why am I not allowed to call AC_CANONICAL_HOST twice? If I try, then I get several lines like configure.ac:160: warning: AC_CANONICAL_HOST invoked multiple times Is there some kind of "if-statement" possible to avoid this warning? Regards Harri

question about AC_CONFIG_SUBDIRS

Hi folks, I've got a question about AC_CONFIG_SUBDIRS: How can I pass a different --prefix to the "sub-configure", e.g. '$(prefix)/submodule' ? Regards Harri ___ Autoconf mailing list Autoconf@gnu.org http://lists.gnu.org/mailman/listinfo/autoconf

AC_PROG_CC_C_O doesn't work with VC++

Hi folks, It seems that AC_PROG_CC_C_O does not work with Microsoft's Visual C++ 13.10.3077. The compiler accepts command lines like cl -c -o conftest.obj conftest.c but command lines like cl -c -o somedir/conftest.obj conftest.c or cl -c -o xyz.obj conftest.c do not wo

Re: AC_PROG_CC_C_O doesn't work with VC++

Stepan Kasal wrote: > Hello, > > On Fri, Jul 01, 2005 at 10:14:28AM +0200, Harald Dunkel wrote: > >>How can I tell autoconf to not use -c and -o together, >>regardless what the test said? > > > Do I guess correctly that you in fact use AM_PROG_CC_C? AM_PROG_C

Re: calling AC_CANONICAL_HOST twice?

Noah Misch wrote: > > If you currently call AC_CANONICAL_HOST from one of your own macros, replace > those calls with `AC_REQUIRE([AC_CANONICAL_HOST])'. If you call it from the > top > level, defun a macro that makes that call and then call your macro. Like > this: > > AC_DEFUN([some_name], [

Re: AC_PROG_CC_C_O doesn't work with VC++

Hi folks, Stepan Kasal wrote: > > the patch attached to this mail (relative to current autoconf CVS) > should fix it. > > OK to commit? > It seems that this patch is still not in CVS. And since the suggested workaround doesn't workaround I am stuck :-(. Any help would be highly appreciated.

Re: AC_PROG_CC_C_O doesn't work with VC++

Hi Stepan, Stepan Kasal wrote: > Hello Harald, > > On Mon, Oct 24, 2005 at 10:35:25AM +0200, Harald Dunkel wrote: > >>It seems that this patch is still not in CVS. And since the >>suggested workaround doesn't workaround I am stuck :-(. > > > I apologize.

Re: AC_PROG_CC_C_O doesn't work with VC++

Hi folks, Ralf Wildenhues wrote: > Hi Harald, > > * Harald Dunkel wrote on Mon, Oct 24, 2005 at 02:19:53PM CEST: > >>I tried the previous patch you had sent some time ago (the >>version with 'conf$[$]'). But this didn't work for Bill's >>cl.e

Re: compile with VC++

Hi Stepan, Stepan Kasal wrote: > > I looked at /usr/share/automake-1.9/compile and I cannot understand > how this could happen. > I think that the parametr to compile should look like > some/path/main.c > which becomes cfile, and then cofile is assigned as > > cofile=`echo "$cfile" | sed -

Re: compile with VC++

Stepan Kasal wrote: > > I looked at /usr/share/automake-1.9/compile and I cannot understand > how this could happen. > I think that the parametr to compile should look like > some/path/main.c > which becomes cfile, and then cofile is assigned as > > cofile=`echo "$cfile" | sed -e 's|^.*/||'

Re: debug builds with NO optimizations

John Calcote wrote: > My point exactly. The autoconf system should reserve a variable that is NOT > the user. Automake has such a facility - AM_CFLAGS. This variable should be > reserved for configure to add flags to the compiler command line based on > higher-level, user-specified options, such

how to define my own configure options

Hi folks, I haven't seen it mentioned anywhere, so hopefully you don't mind me asking? What is the recommended procedure to define my own configure options in configure.ac, e.g. "--report" to list the settings found, or "--shorthelp" to list just the "non-standard" options, ignoring or including

Re: Installing with Autotools under Windows?

Hi Hans, Is it possible that you are looking for an install manager? Maybe http://installjammer.com/ is an option? Just a suggestion, of course. Regards Harri = Hans Derkits wrote: Dear participants, I would be astonished, if my pr