bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libtool-1.4.2


From: Carlo Wood
Subject: libtool-1.4.2
Date: Fri, 26 Jul 2002 16:35:14 +0200
User-agent: Mutt/1.2.5i

I am stuck with my project due to a serious
problem with libtool 1.4.2.

The problem shows as:

make[2]: Entering directory `/home/carlo/c++/libecc'
source='ecc_rng.cc' object='libecc_la-ecc_rng.lo' libtool=yes \
depfile='.deps/libecc_la-ecc_rng.Plo' tmpdepfile='.deps/libecc_la-ecc_rng.TPlo' 
\
depmode=gcc3 /bin/sh ./depcomp \
/bin/sh ./libtool --mode=compile g++ -DHAVE_CONFIG_H  -I./include -I./include   
-g -pipe -Wall -Woverloaded-virtual -Wundef -Wpointer-arith -Wwrite-strings 
-Werror  -c -o libecc_la-ecc_rng.lo `test -f ecc_rng.cc || echo './'`ecc_rng.cc
g++ -DHAVE_CONFIG_H -I./include -I./include -g -pipe -Wall -Woverloaded-virtual 
-Wundef -Wpointer-arith -Wwrite-strings -Werror -c ecc_rng.cc
-MT libecc_la-ecc_rng.lo -MD -MP -MF .deps/libecc_la-ecc_rng.TPlo  -fPIC -DPIC
mv -f libecc_la-ecc_rng.o libecc_la-ecc_rng.lo
mv: cannot stat `libecc_la-ecc_rng.o': No such file or directory
make[2]: *** [libecc_la-ecc_rng.lo] Error 1

Clearly, that 'mv' shouldn't be there :/

The relevant lines which causes the above error, in 'Makefile' are:

------------------------------------------------------
SHELL = /bin/sh
srcdir = .
top_builddir = .
DEPDIR = .deps
CXXDEPMODE = depmode=gcc3
LIBTOOL = $(SHELL) $(top_builddir)/libtool
CXX = g++
DEFS = -DHAVE_CONFIG_H
DEFAULT_INCLUDES =
INCLUDES = -I$(top_builddir)/include -I$(srcdir)/include
CPPFLAGS =
DEBUGOPTS = -g
EXTRAOPTS =  -pipe
WARNOPTS = -Wall -Woverloaded-virtual -Wundef -Wpointer-arith -Wwrite-strings 
-Werror
libecc_la_CXXFLAGS = $(DEBUGOPTS) $(EXTRAOPTS) $(WARNOPTS)
CXXFLAGS =

libecc_la-ecc_rng.lo: ecc_rng.cc
        source='ecc_rng.cc' object='libecc_la-ecc_rng.lo' libtool=yes \
        depfile='$(DEPDIR)/libecc_la-ecc_rng.Plo' 
tmpdepfile='$(DEPDIR)/libecc_la-ecc_rng.TPlo' \
        $(CXXDEPMODE) $(depcomp) \
        $(LIBTOOL) --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) 
$(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(libecc_la_CXXFLAGS) $(CXXFLAGS) -c -o 
libecc_la-ecc_rng.lo `test -f ecc_rng.cc || echo '$(srcdir)/'`ecc_rng.cc
------------------------------------------------------

By looking at this, we can conclude that it is not
a bug of autoconf.  This problem certainly is not
related to the variables being set (SHELL till CXXFLAGS above).

Makefile was generated by 'configure' from Makefile.in, and
the relevant line there is:

------------------------------------------------------
libecc_la-ecc_rng.lo: ecc_rng.cc
@AMDEP_TRUE@    source='ecc_rng.cc' object='libecc_la-ecc_rng.lo' libtool=yes 
@AMDEPBACKSLASH@
@AMDEP_TRUE@    depfile='$(DEPDIR)/libecc_la-ecc_rng.Plo' 
tmpdepfile='$(DEPDIR)/libecc_la-ecc_rng.TPlo' @AMDEPBACKSLASH@
@AMDEP_TRUE@    $(CXXDEPMODE) $(depcomp) @AMDEPBACKSLASH@
        $(LIBTOOL) --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) 
$(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(libecc_la_CXXFLAGS) $(CXXFLAGS)
------------------------------------------------------

This part was generated by automake-1.5 from Makefile.am
which looks like:

======================================================
## Process this file with automake to generate Makefile.in

AUTOMAKE_OPTIONS = foreign

SUBDIRS = include

BUILT_SOURCES address@hidden@ libecc.spec
EXTRA_DIST = LICENSE $(BUILT_SOURCES)
DISTCLEANFILES =

address@hidden@
EXTRAOPTS = @EXTRAOPTS@
DEBUGOPTS = @DEBUGOPTS@
WARNOPTS = @WARNOPTS@
CXXFLAGS =
INCLUDES = -I$(top_builddir)/include -I$(srcdir)/include
DEFAULT_INCLUDES =

LIBECC = libecc.la

lib_LTLIBRARIES = $(LIBECC)

libecc_la_CXXFLAGS = $(DEBUGOPTS) $(EXTRAOPTS) $(WARNOPTS)
libecc_la_SOURCES = ecc_rng.cc

libecc_la_LDFLAGS = -version-info $(VERSIONINFO)
======================================================

Imho, because there is nothing special here, we can conclude that
the bug must be in the script 'libtool'.

The libtool script contains:

PACKAGE=libtool
VERSION=1.4.2
TIMESTAMP=" (1.922.2.54 2001/09/11 03:33:37)"

I guess there is no need to attach it here (you have it yourself).

Please tell me asap what is a work around for this problem,
so that I can continue.

-- 
Carlo Wood <address@hidden>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]