search for: libtool

On Thu, Jul 19, 2001 at 02:56:11PM -0700, collver@linuxfreemail.com wrote: > On Thu, Jul 19, 2001 at 05:01:07PM -0400, Matt Zimmerman wrote: > > Once I removed that, it also seems to hate the .nasm extension: > > > > /bin/sh ../../../libtool --mode=compile \ > > sh ../../../strip_fPIC.sh nasm -f elf -d OBJ_FORMAT_elf cpu_asm.nasm > > libtool: compile: cannot determine name of library object from `cpu_asm.nasm' > > > > Is there some pressing reason to use libtool to compile these objects, rather >...

Hello Dovecot users, There haven't been that many Pigeonhole developments lately, not even really significant bugs were reported. That is why this release is pretty small in terms of changes. However, one issue got some attention: the fact that not recompiling Pigeonhole for Dovecot v2.0.3 would result in rather interesting message delivery. Normally, Dovecot would complain about a

Hello Dovecot users, There haven't been that many Pigeonhole developments lately, not even really significant bugs were reported. That is why this release is pretty small in terms of changes. However, one issue got some attention: the fact that not recompiling Pigeonhole for Dovecot v2.0.3 would result in rather interesting message delivery. Normally, Dovecot would complain about a

On Thu, Jul 19, 2001 at 04:58:44PM -0400, Matt Zimmerman wrote: > On Thu, Jul 19, 2001 at 10:38:14AM -0700, Josh Coalson wrote: > > > So, last chance to checkout from CVS and break it! > > Also, my libtool doesn't seem to recognize --tag=CC. What is its purpose? > > /bin/sh ../../../libtool --tag=CC --mode=compile \ > sh ../../../strip_fPIC.sh nasm -f elf -d OBJ_FORMAT_elf cpu_asm.nasm > libtool: unrecognized option `--tag=CC' > Try `libtool --help' for more infor...

I'm trying to build an executable for a program I wrote. The compilation steps go well, but the linking step fails with a libtool "version mismatch" error. My linking command has this prefix: /path/to/R/bin/R CMD LINK gcc -g -std=gnu99 ... etc. The error looks like this: libtool: Version mismatch error. This is libtool 2.2, but the libtool: definition of this LT_INIT comes from libtool 2.2.6. libtool: You shoul...

...ome unknown (but probably relatively recent) version that will work (or, at least, it thinks it will work, and i suspect that it knows better than you do) I'm raising this issue because i've encountered strange errors in makefile (generated with autogen and configure). At first i suspected libtool to be the troublemaker, but eventually i was only able to resolve them when i hacked autogen.sh to call the wrappers for automake and aclocal instead of using explicit 1.7 (which is what it does, since AM_NEEDED evaluates to 1.7). This is the first time i'm getting such errors. It is probably...

...le building PoCC. Here is the error, ---------------------------------------------------------- make[1]: Entering directory `/tmp/chenwj/pocc-1.0-rc3.1/optimizers/letsee-0.2.0-pre/letsee' make[2]: Entering directory `/tmp/chenwj/pocc-1.0-rc3.1/optimizers/letsee-0.2.0-pre/letsee' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../letsee/include/letsee -I.. -I.. -I../letsee/include -I../letsee/include +-I/tmp/chenwj/pocc-1.0-rc3.1/math/install-fm/include -I/tmp/chenwj/pocc-1.0-rc3.1/analyzers/install-candl/include +-I/tmp/chenwj/pocc-1.0-rc3.1/driver/install-pocc/includ...

We're planning to contribute an LLVM version of Apple's libtool utility. To quote its man page, "Libtool with -static is intended to replace ar(5) and ranlib". In other words, libtool is the preferred tool to create archives for Apple platforms, and it also has good defaults for that platform (e.g. automatically creating a table of contents with the r...

...nu loading site script './config.site' loading build-specific script './config.site' ./configure: line 2982: syntax error near unexpected token `blas' ./configure: line 2982: ` withval=$with_blas; R_ARG_USE(blas)' OK.. there's a recipe that oen can use, starting with: libtoolize --force but you get: A sequence typical found out there, starting withlibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `tools'. libtoolize: linking file `tools/ltmain.sh' libtoolize: You should add the contents of the following files to `aclocal.m4': libtoolize: `/usr/sh...

I'm trying to build upstream source on RHEL 7.5 and get this error: # autoreconf -i libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copyin...

I've encountered a new problem building gluster-2.0.1 that I did not have with gluster-2.0.0rc8. This is on a mandriva-2008.1-x86_64 system. ../../libtool: line 466: CDPATH: command not found ../../libtool: line 1144: func_opt_split: command not found libtool: Version mismatch error. This is libtool 2.2.6 Debian-2.2.6a-4, but the libtool: definition of this LT_INIT comes from an older release. libtool: You should recreate aclocal.m4 with macros fro...

...ot;icecast"; it's not very short... Thanks in advance for any help. --- $~/icecast/icecast> ./autogen.sh Checking for automake version found automake found aclocal Generating configuration files for ices, please wait.... aclocal -I m4 aclocal: configure.in: 13: macro `AM_PROG_LIBTOOL' not found in library autoheader autoheader: error: AC_CONFIG_HEADERS not found in configure.in libtoolize --automake automake --add-missing configure.in: no proper invocation of AM_INIT_AUTOMAKE was found. configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE, config...

Hi, looking on the build scripts, I noticed on configure.ac ## <FIXME> ## Completely disable using libtool for building shlibs until libtool ## fully supports Fortran and C++. ## AC_ARG_WITH([libtool], ## [AS_HELP_STRING([--with-libtool],[use libtool for building shared libraries @ <:@yes@:>@])], ## [use_libtool="${withval}"], ## [use_libtool=yes]) ## AM_CONDITIONAL(USE_LIBTOOL, [test &...

I'm not sure if this is related to me updating to gcc 4.6.0 or not, but in the gnulib/lib directory I get an error which comes down to the following libtool command running: $ ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT c-ctype.lo -MD -MP -MF .deps/c-ctype.Tpo -c -o c-ctype.lo c-ctype.c ../../libtool: line 2075: c-ctype.c: command not found libtool: compile: gcc -std=gnu99 -std=gnu99 -DHAVE_C...

Hi. I want to add some code to flac and am having trouble building it out of cvs. I've had several problems, most of which were pretty easy to work around or had already been discussed here. But this one has me stumped (though I am admittedly new to autoconf, automake, and libtool). Here's the problem. autoconf does not see any definition for AC_PROG_LIBTOOL. There is such a definition in <libtool directory>/share/aclocal/libtool.m4, but autoconf doesn't seem to be aware of that. I don't know how to tell it to look there; autoconf doesn't appear to...

On Sat, Jul 21, 2001 at 04:06:14PM -0400, Matt Zimmerman wrote: > Argh. Maybe libtool will have to get involved after all. I'll work on it > this afternoon. I think I give up. automake and libtool assume that the compiler will be able to assemble stuff, and compilers don't generally understand NASM input. I don't like the strip_fPIC bit, since just about anything...

...e automake you wish to" + echo "use in the environment used to invoke $0," + echo "for example:" + echo " $ env AUTOMAKE=/path/to/automake ACLOCAL=/path/to/aclocal $0" + echo " or $ env AUTOMAKE=automake18 $0" exit 1 } fi echo -n "checking for libtool... " -for LIBTOOLIZE in libtoolize glibtoolize nope; do - ($LIBTOOLIZE --version) < /dev/null > /dev/null 2>&1 && break +LIBTOOLIZE=${LIBTOOLIZE:-libtoolize} +for libtoolize in ${LIBTOOLIZE} libtoolize glibtoolize nope; do + ($libtoolize --version) < /dev/null > /d...

...static linking at some point (I thought it was just 10.3, > but apparently not). They claim it was never supported, but this > is (obviously) just a bug. There's no static version of the library > in question, so static linking against the system libs always fails > and no one told libtool. > > The fix is to comment out the line > > LDFLAGS = -all-static > > in vorbis/examples/Makefile.am and rebuild. > >> When I google this I can find lots of instances of makes being unable >> to locate this file on OSX, but very little help that is applicable to &gt...

Hello, with rc6 on FreeBSD 6.1-STABLE, I encounter the following when running make after the usual configure [ Note : that worked with rc5 ] /usr/local/bin/zsh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -L/usr/local/lib -o dovecot-auth -export-dynamic auth.o auth-cache.o auth-client-connection.o auth-master-connection.o auth-master-l...

On Thu, Jul 19, 2001 at 04:58:44PM -0400, Matt Zimmerman wrote: > On Thu, Jul 19, 2001 at 10:38:14AM -0700, Josh Coalson wrote: > > > So, last chance to checkout from CVS and break it! > > Also, my libtool doesn't seem to recognize --tag=CC. What is its purpose? > > /bin/sh ../../../libtool --tag=CC --mode=compile \ > sh ../../../strip_fPIC.sh nasm -f elf -d OBJ_FORMAT_elf cpu_asm.nasm > libtool: unrecognized option `--tag=CC' > Try `libtool --help' for more infor...