On Wednesday, February 5, 2003, at 10:46 PM, Robert Boehne wrote:
In an older version of Libtool, a library built with -module is
linked with:
cc -flat_namespace -undefined suppress -o .libs/libdb_tcl-4.2.so *.lo
-lc -dynamiclib -install_name
/Users/rboehne/testdb/lib/libdb_tcl-4.2.so
That is
Hello,
I'm having problems with Mac OS/X in CVS Libtool, and I wonder
if some of you more familiar with the platform could help out.
In an older version of Libtool, a library built with -module is
linked with:
cc -flat_namespace -undefined suppress -o .libs/libdb_tcl-4.2.so *.lo
-lc -dynamiclib -
t; freedom it gives its assimilated conformists." -- Abbie Hoffman
>
>
> Name:
>libtool.m4.ccc.cvshead.20030205.p
On Tuesday, February 4, 2003, at 09:46 PM, Albert Chin wrote:
I think we should support the two-level namespace, even if it is
OSX-specific. I look at libtool more as a way to easily build shared
libraries across multiple platforms.
Think about AIX. An AIX shared library (non-brtl) can contain *
FWIW, "current" CVS (most recent changelog entry when I checkedout was
"2003-02-04 Nick Hudson ") has no new test failures
on cygwin.
autoconf-2.57
automake-1.7.2
cygwin-1.3.18-1
gcc-3.2-3
binutils-20021117-1
the only existing testsuite failures are two longstanding ones,
build-relink2 and q
On Wed, 5 Feb 2003, Robert Boehne wrote:
>
> Yeah, I think this is too much. 's/main/cos/' fixes the problem
> without risking anything.
> With Bob's approval I'm going to check this patch in.
Approved! :-)
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.s
Albert Chin wrote:
>
> Is this too much:
> AC_CHECK_FUNC(cos, , AC_CHECK_LIB(m, cos, LIBM="$LIBM -lm"))
>
> We could do the same for:
> AC_CHECK_LIB(mw, _mwvalidcheckl, LIBM="-lmw").
>
> --
> albert chin ([EMAIL PROTECTED])
Yeah, I think this is too much. 's/main/cos/' fixes the problem
w
Here is a trivial patch to add Compaq's alpha c compiler (ccc) to
libtool.m4. This is against CVS head.
Cheers,
Bob McElrath [Univ. of Wisconsin at Madison, Department of Physics]
"You measure democracy by the freedom it gives its dissidents, not the
freedom it gives its assimilated conf
On Wed, Feb 05, 2003 at 08:57:08PM -0600, Robert Boehne wrote:
> Index: libtool.m4
> ===
> RCS file: /cvsroot/libtool/libtool/libtool.m4,v
> retrieving revision 1.297
> diff -u -r1.297 libtool.m4
> --- libtool.m45 Feb 2003 07:0
On Wed, 5 Feb 2003, Robert Boehne wrote:
> How about this patch?
The patch looks great to me.
Bob
> The math library is not actually used by anything but the
> test suite in Libtool, so as long as the C standard and
> common practice put "cos" in -lm it's all good.
>
> ChangeLog entry:
>
> 2003
How about this patch?
The math library is not actually used by anything but the
test suite in Libtool, so as long as the C standard and
common practice put "cos" in -lm it's all good.
ChangeLog entry:
2003-02-05 Robert Boehne <[EMAIL PROTECTED]>
* libtool.m4 (AC_CHECK_LIBM): Search for
>>> "Robert" == Robert Boehne <[EMAIL PROTECTED]> writes:
Robert> Alexandre,
Robert> Snapshots of CVS are made daily and reside at
Robert> ftp://alpha.gnu.org/pub/gnu/cvs/libtool.tgz
CVS snapshots are differents from `make dist' tarballs. The
former still requires maintainer tools like Autoco
Alexandre,
Snapshots of CVS are made daily and reside at
ftp://alpha.gnu.org/pub/gnu/cvs/libtool.tgz
I'm not sure where to announce a pending release other
than here, but I had just intended to re-release after
bugs were fixed & found in 1.5. If you have a suggestion
on where to announce the pre-
On Wed, 5 Feb 2003, Praveen Jain wrote:
> >>
> >> The main motivation is to reduce the build time
> >> approximately by a factor of 2 which would be a
> >> tremendous help for us.
> >
> >--disable-shared or --disable-static. If you want static and shared,
> >you don't have a choice.
>
> Where do yo
At 04:18 PM 2/5/2003 -0600, Albert Chin wrote:
>On Wed, Feb 05, 2003 at 02:11:39PM -0800, Asim Suter wrote:
>> I see that libtool compiles every C source file two times
>> 1) once to generate ".lo" files
>> 2) second time to generate ".o" files
>>
>> Is it possible to "tell" libtool to generate
On Wed, Feb 05, 2003 at 03:00:39PM -0600, Bob Friesenhahn wrote:
> I posted a detailed message to [EMAIL PROTECTED] and
> [EMAIL PROTECTED] but there has been no response at all so I will
> post again.
>
> CVS libtool.m4 contains lines like
>
> AC_CHECK_LIB(m, main, LIBM="-lm")
>
> and
>
On Wed, Feb 05, 2003 at 02:11:39PM -0800, Asim Suter wrote:
> I see that libtool compiles every C source file two times
> 1) once to generate ".lo" files
> 2) second time to generate ".o" files
>
> Is it possible to "tell" libtool to generate
> only one type of object file ? My belief is that
>
Hello,
We build shared libraries and executables on
a Linux system for Pentium processor.
We use libtool along with automake and autoconf
as part of our build infrastructure.
I see that libtool compiles every C source file two times
1) once to generate ".lo" files
2) second time to generate "
On Wed, 5 Feb 2003, Bob Friesenhahn wrote:
>
> The solution seems to be to either fix autoconf so that it emmits a
> different test program for the special case where 'main' is tested for
> (which is in fact a valid test!), or to fix libtool.m4 so that it
> requests a known symbol from the library
I posted a detailed message to [EMAIL PROTECTED] and
[EMAIL PROTECTED] but there has been no response at all so I will
post again.
CVS libtool.m4 contains lines like
AC_CHECK_LIB(m, main, LIBM="-lm")
and
AC_CHECK_LIB(ltdl, main, ... blah
Unfortunately, these result in Autoconf generati
Albert Chin wrote:
On Wed, Feb 05, 2003 at 06:04:06PM +0100, Roberto Bagnara wrote:
when I do make install, the files installed have the wrong name.
Here is what I see
$ ls
libppl. libppl.a libppl_c..0.1.0 libppl.la
libppl..0libppl_c.libppl_c.a
libppl..0.2.0
I
>>> "Robert" == Robert Boehne <[EMAIL PROTECTED]> writes:
Robert> Hello,
Robert> I'm just about to make the release of Libtool 1.5. If anyone would
Robert> like to test the current CVS on their favorite platform and report
Robert> any problems, please do so! If not, your woes may have to wai
On Wed, Feb 05, 2003 at 06:04:06PM +0100, Roberto Bagnara wrote:
> when I do make install, the files installed have the wrong name.
> Here is what I see
>
> $ ls
> libppl. libppl.a libppl_c..0.1.0 libppl.la
> libppl..0libppl_c.libppl_c.a
> libppl..0.2.0
>
> It lo
On Tue, Feb 04, 2003 at 01:10:54AM -0600, Robert Boehne wrote:
> I'm just about to make the release of Libtool 1.5. If anyone would
> like to test the current CVS on their favorite platform and report
> any problems, please do so! If not, your woes may have to wait for
> 1.5.1.
What date do you
Hi there,
when I do make install, the files installed have the wrong name.
Here is what I see
$ ls
libppl. libppl.a libppl_c..0.1.0 libppl.la
libppl..0libppl_c.libppl_c.a
libppl..0.2.0
It looks like "so" was omitted from "libppl.so" and similarly
for the other
On Wed, 5 Feb 2003, Richard Dawe wrote:
> Hello.
>
> I've been trying to bootstrap a CVS check-out of libtool and I've hit some
> problems. The problems occur when I run the "boostrap" script. I'm using the
> DJGPP ports of autoconf 2.57 and automake 1.7.2.
>
> Firstly, I keep getting the followin
ArtBarker.com
Your #1 Art-Related Marketplace
(http://www.ArtBarker.com )
Just in case you were interested, we are currently running a
Winter special of HALF OFF the listed advertising rates (for as
many months as you wish to list!), so please contact us if you
would like more details on adve
Hello.
Robert Boehne wrote:
> It looks to me like automake isn't installed correctly. Automake
> provides macros like AM_INIT_AUTOMAKE to Autoconf, so Autoconf
> needs to find them.
It works with other packages like GNU coreutils 4.5.4. That's why I'm puzzled
by this. I'll try to dig a little de
Richard,
It looks to me like automake isn't installed correctly. Automake
provides macros like AM_INIT_AUTOMAKE to Autoconf, so Autoconf
needs to find them.
HTH,
Robert
Richard Dawe wrote:
>
> Hello.
>
> I've been trying to bootstrap a CVS check-out of libtool and I've hit some
> problems. T
Hello.
I've been trying to bootstrap a CVS check-out of libtool and I've hit some
problems. The problems occur when I run the "boostrap" script. I'm using the
DJGPP ports of autoconf 2.57 and automake 1.7.2.
Firstly, I keep getting the following message:
configure.ac: `AM_INIT_AUTOMAKE' must be
Albert Chin writes:
> On Tue, Feb 04, 2003 at 04:04:29PM +, Lars Hecking wrote:
> > On Solaris 7/8, this list of objects is too long for the native sed,
> > and linking fails (some error messages about "line too long"). I reported
> > this as a bug and was told to use GNU sed instead.
>
> F
Hello,
I just tried libtool CVS version (with cvs -z3 up -PAd)
this is the make check output:
Platform is FreeBSD 5.0-RELEASE
FAIL: demo-make.test
FAIL: depdemo-make.test
FAIL: mdemo-inst.test
FAIL: mdemo-unst.test
=
4 of 101 tests failed
=
I can provide mo
32 matches
Mail list logo
