Libtool 2.2.4 (Stable branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Libtool 2.2.4 (Stable branch)
# 1  
Old 05-06-2008
Libtool 2.2.4 (Stable branch)

GNU libtool is a generic library support script. Libtool hides the complexity of using shared and static libraries behind a consistent, portable interface. Libtool supports building static libraries on all platforms. License: GNU General Public License (GPL) Changes:
The new libtoolize option --no-warn has been added. The --debug, --no-warn, --quiet, and --verbose options can be passed to libtoolize through the environment variable LIBTOOLIZE_OPTIONS. Several bugs with macros have been fixed.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Aclocal and libtool error -- macro `AM_PROG_LIBTOOL' not found in library

The software I'm trying to install uses macros with autoconf, aclocal, libtool, autoheader, and automake. What seems to be going on is an error between libtool and aclocal. From what I understand when I run aclocal, which is in /usr/bin, it searches a different directory for the libtool.m4 which is... (0 Replies)
Discussion started by: bphqk3
0 Replies

2. UNIX for Dummies Questions & Answers

Trying to install libtool from source - newbie

Hey all, I am trying to configure software (Open Cascade) and I am receiving the following error: configure.ac:24: warning: macro `AM_PROG_LIBTOOL' not found in library I know I must be missing libtool, however, when I try and grab libtool (a lot of sites have the proper tarball and... (2 Replies)
Discussion started by: bphqk3
2 Replies

3. UNIX for Dummies Questions & Answers

Creating fat files: Lipo vs libtool

I wonder what would be the difference when using: lipo -create i386/libAwesome.a armv7/libAwesome.a -o fat/libAwesome.a and libtool -static i386/libAwesome.a armv7/libAwesome.a -o fat/libAwesome.a I have the impression that lipo is more general, and it will simply stick two files from... (0 Replies)
Discussion started by: nacho4d
0 Replies

4. Programming

Execution problem with Libtool Versioning control

Hi, Is anybody familiar with libtool could explain me the following issue.? I've created a small factorial program(fact_impl.c, fact_appln.c & fact.h) in order to know about this libtool. >>> fact.h #include<stdio.h> #include<math.h> extern unsigned int fact_num(unsigned int num);... (0 Replies)
Discussion started by: Parameswaran
0 Replies

5. Programming

Question re: remember to run `libtool --finish ...`

Hi. I port/package software for AIX and often get this message during "make install" libtool: install: warning: remember to run `libtool --finish /some/directory` I have run the command manually, and not run it. I am unable to see what difference it is making. Questions: What is the... (1 Reply)
Discussion started by: MichaelFelt
1 Replies

6. UNIX for Dummies Questions & Answers

Rapache, libtool, and Make on Solaris 10

I'd like to first off state that this is my second day using Solaris, so go easy on me. I am trying to install rapache on a Solaris 10 server, and I am running into some frustrating roadblocks. When running configure, I see that it creates its own libtool and sets the tag (according to the... (0 Replies)
Discussion started by: gadonj18
0 Replies

7. Linux

libtool compile mode,how to set include path?

Hi all I want to compile a source gt_util.c into a lo file, I use libtool gcc -g -O -c gt_util.c -I./include but it prompts me : cannot determin name of library object from 'include' how should I use the tool to compile a source to .lo file? Thanks. (0 Replies)
Discussion started by: steven_TTG
0 Replies
Login or Register to Ask a Question
APR-1-CONFIG(1) 						   User Commands						   APR-1-CONFIG(1)

NAME
apr-1-config - Return metainformation about apr library SYNOPSIS
apr-1-config [OPTION] DESCRIPTION
The apr-1-config program is used to retrieve information about the apr library in the system. It is typically used to compile and link against the library. When linking with libtool, an application should do something like: APR_LIBS="`apr-1-config --link-libtool --libs`" or when linking directly: APR_LIBS="`apr-1-config --link-ld --libs`" An application should use the results of --cflags, --cppflags, --includes, and --ldflags in their build process. OPTIONS
Known values for OPTION are: --prefix[=DIR] change prefix to DIR --bindir print location where binaries are installed --includedir print location where headers are installed --cc print C compiler name --cpp print C preprocessor name and any required options --cflags print C compiler flags --cppflags print C preprocessor flags --includes print include information --ldflags print linker flags --libs print additional libraries to link against --srcdir print APR source directory --installbuilddir print APR build helper directory --link-ld print link switch(es) for linking to APR --link-libtool print the libtool inputs for linking to APR --shlib-path-var print the name of the shared library path env var --apr-la-file print the path to the .la file, if available --apr-so-ext print the extensions of shared objects on this platform --apr-lib-target print the libtool target information --apr-libtool print the path to APR's libtool --version print the APR's version as a dotted triple --help print the help AUTHOR
This manual page was written by Vincent Danjean <Vincent.Danjean@ens-lyon.org> for the Debian project (but may be used by others). apr-1-config 1.2.2 March 2006 APR-1-CONFIG(1)