Ralf Wildenhues | 1 Nov 2009 09:36
Picon
Picon

Re: [libtool 2.2.6] testsuite: 41 52 53 54 56 57 58 59 60 61 68 69 70 failed

Hello root,  ;-)

* root wrote on Mon, Oct 26, 2009 at 04:04:32PM CET:
> ## ------------------------- ##
> ## libtool 2.2.6 test suite. ##
> ## ------------------------- ##
> 
> testsuite: command line was:
>   $ /home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/tests/testsuite MAKE=make CC=gcc CFLAGS=-g
-O2 CPP=gcc -E CPPFLAGS= LD=/usr/bin/ld LDFLAGS= LIBS=-ldl  LN_S=ln -s NM=/usr/bin/nm -B
RANLIB=ranlib STRIP=strip OBJEXT=o EXEEXT= SHELL=/bin/sh CONFIG_SHELL=/bin/sh CXX=g++
CXXFLAGS=-g -O2 CXXCPP=g++ -E F77=g77 FFLAGS=-g -O2 FC=gfortran FCFLAGS=-g -O2 GCJ=gcj GCJFLAGS=-g
-O2 _lt_pkgdatadir=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6
LIBTOOLIZE=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/libtoolize
LIBTOOL=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/libtool tst_aclocaldir=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/libltdl/m4

[...]

> ERROR: 72 tests were run,
> 16 failed (3 expected failures).
> 2 tests were skipped.
> 
> ## ------------------------ ##
> ## Summary of the failures. ##
> ## ------------------------ ##
> Failed tests:
> libtool 2.2.6 test suite test groups:
> 
>  NUM: FILE-NAME:LINE     TEST-GROUP-NAME
>       KEYWORDS
(Continue reading)

Sergei Steshenko | 1 Nov 2009 12:30
Picon
Favicon

Re: [libtool 2.2.6] testsuite: 41 52 53 54 56 57 58 59 60 61 68 69 70 failed


--- On Sun, 11/1/09, Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> wrote:

> From: Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de>
> Subject: Re: [libtool 2.2.6] testsuite: 41 52 53 54 56 57 58 59 60 61 68 69 70 failed
> To: "root" <root <at> wcas1.uwaterloo.ca>
> Cc: bug-libtool <at> gnu.org
> Date: Sunday, November 1, 2009, 1:36 AM
> Hello root,  ;-)
> 
> * root wrote on Mon, Oct 26, 2009 at 04:04:32PM CET:
> > ## ------------------------- ##
> > ## libtool 2.2.6 test suite. ##
> > ## ------------------------- ##
> > 
> > testsuite: command line was:
> >   $
> /home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/tests/testsuite
> MAKE=make CC=gcc CFLAGS=-g -O2 CPP=gcc -E CPPFLAGS=
> LD=/usr/bin/ld LDFLAGS= LIBS=-ldl  LN_S=ln -s
> NM=/usr/bin/nm -B RANLIB=ranlib STRIP=strip OBJEXT=o EXEEXT=
> SHELL=/bin/sh CONFIG_SHELL=/bin/sh CXX=g++ CXXFLAGS=-g -O2
> CXXCPP=g++ -E F77=g77 FFLAGS=-g -O2 FC=gfortran FCFLAGS=-g
> -O2 GCJ=gcj GCJFLAGS=-g -O2
> _lt_pkgdatadir=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6
> LIBTOOLIZE=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/libtoolize
> LIBTOOL=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/libtool
> tst_aclocaldir=/home/hzs/MyEclipseWorkspace/xine/libtool-2.2.6/libltdl/m4
> 
> [...]
(Continue reading)

Ralf Wildenhues | 1 Nov 2009 12:33
Picon
Picon

Re: [libtool 2.2.6] testsuite: 41 52 53 54 56 57 58 59 60 61 68 69 70 failed

Hello Sergei,

* Sergei Steshenko wrote on Sun, Nov 01, 2009 at 12:30:06PM CET:
> --- On Sun, 11/1/09, Ralf Wildenhues wrote:
> > Thanks for the report.  Do you have Autoconf 2.59
> > installed?
> > Then these failures should be fixed by either updating to a
> > newer
> > Autoconf release, or by this post-2.2.6 patch:
> > <http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=8ae796bacd9b57cdcb68927d93d696552187b0bb>

> Shouldn't 'configure' check for the correct 'autoconf' version in the first
> place ?

Well, the Libtool macros should work with any non-ancient Autoconf
version.  Here, we messed up and accidentally broke support for 2.59.

If it turns out to be impossible to support some older Autoconf version,
then yes we should ensure that it is not used.  Currently, LT_INIT has
  AC_PREREQ([2.58])dnl We use AC_INCLUDES_DEFAULT

which I think should be sufficient though.

Thanks,
Ralf
Stanislav Brabec | 4 Nov 2009 19:06
Picon
Favicon

[libtool 2.2.6] linking -static with uninstalled shared library generates invalid rpath

When linking a binary which contains -static in its LDFLAGS and the
library is linked against an uninstalled library which does not contain
-static in its LDFLAGS and configure was called with --disable-static,
libtool generates invalid command line that embeds RPATH to the
uninstalled shared library location.

It could be considered even as a security issue, as such binary may load
malicious library from a possibly world writable area.

Attachment shows an example, where the final linking expands to:

/bin/sh ./libtool --tag=CC   --mode=link gcc  -g -O2 -static  -o hallolib hallolib-hallolib.o
./libhallo/libhallo.la 
libtool: link: gcc -g -O2 -o hallolib hallolib-hallolib.o  ./libhallo/.libs/libhallo.so -Wl,-rpath -Wl,/home/sbrabec/libinvalid/libhallo/.libs

Guessing thet the correct line should be:
libtool: link: gcc -g -O2 -o .libs/hallolib hallolib-hallolib.o  ./libhallo/.libs/libhallo.so
and wrapper should be written

--

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sbrabec <at> suse.cz
Lihovarská 1060/12           tel: +420 284 028 966, +49 911 740538747
190 00 Praha 9                                  fax: +420 284 028 951
Czech Republic                                    http://www.suse.cz/
(Continue reading)

Bob Friesenhahn | 4 Nov 2009 19:25
Picon
Picon
Gravatar

Re: [libtool 2.2.6] linking -static with uninstalled shared library generates invalid rpath

On Wed, 4 Nov 2009, Stanislav Brabec wrote:

> When linking a binary which contains -static in its LDFLAGS and the
> library is linked against an uninstalled library which does not contain
> -static in its LDFLAGS and configure was called with --disable-static,
> libtool generates invalid command line that embeds RPATH to the
> uninstalled shared library location.
>
> It could be considered even as a security issue, as such binary may load
> malicious library from a possibly world writable area.

Is this true after the library/program has been installed with libtool 
using --mode=finish?

Bob

>
> Attachment shows an example, where the final linking expands to:
>
> /bin/sh ./libtool --tag=CC   --mode=link gcc  -g -O2 -static  -o hallolib hallolib-hallolib.o ./libhallo/libhallo.la
> libtool: link: gcc -g -O2 -o hallolib hallolib-hallolib.o  ./libhallo/.libs/libhallo.so -Wl,-rpath -Wl,/home/sbrabec/libinvalid/libhallo/.libs
>
> Guessing thet the correct line should be:
> libtool: link: gcc -g -O2 -o .libs/hallolib hallolib-hallolib.o  ./libhallo/.libs/libhallo.so
> and wrapper should be written
>
> -- 
> Best Regards / S pozdravem,
>
> Stanislav Brabec
(Continue reading)

Stanislav Brabec | 4 Nov 2009 19:38
Picon
Gravatar

Re: [libtool 2.2.6] linking -static with uninstalled shared library generates invalid rpath

Bob Friesenhahn wrote:
> On Wed, 4 Nov 2009, Stanislav Brabec wrote:
> 
> > When linking a binary which contains -static in its LDFLAGS and the
> > library is linked against an uninstalled library which does not contain
> > -static in its LDFLAGS and configure was called with --disable-static,
> > libtool generates invalid command line that embeds RPATH to the
> > uninstalled shared library location.

> Is this true after the library/program has been installed with libtool 
> using --mode=finish?

Yes:

sbrabec:~/libinvalid/DESTDIR/usr/local/bin> scanelf -r hallolib
 TYPE   RPATH FILE
ET_EXEC /home/sbrabec/libinvalid/libhallo/.libs hallolib

--

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sbrabec <at> suse.cz
Lihovarská 1060/12           tel: +420 284 028 966, +49 911 740538747
190 00 Praha 9                                  fax: +420 284 028 951
Czech Republic                                    http://www.suse.cz/
Ralf Wildenhues | 4 Nov 2009 20:36
Picon
Picon

Re: [libtool 2.2.6] linking -static with uninstalled shared library generates invalid rpath

Hello Stanislav,

* Stanislav Brabec wrote on Wed, Nov 04, 2009 at 07:38:34PM CET:
> Bob Friesenhahn wrote:
> > On Wed, 4 Nov 2009, Stanislav Brabec wrote:
> > 
> > > When linking a binary which contains -static in its LDFLAGS and the
> > > library is linked against an uninstalled library which does not contain
> > > -static in its LDFLAGS and configure was called with --disable-static,
> > > libtool generates invalid command line that embeds RPATH to the
> > > uninstalled shared library location.
> 
> > Is this true after the library/program has been installed with libtool 
> > using --mode=finish?
> 
> Yes:

Thanks for the bug report.  Confirmed.  Below is a test case to expose
it.

Cheers,
Ralf

2009-11-04  Stanislav Brabec  <sbrabec <at> suse.cz>
            Ralf Wildenhues  <Ralf.Wildenhues <at> gmx.de>

	* tests/static.at (--tag=disable-static and -static): New test.

diff --git a/tests/static.at b/tests/static.at
index f59b124..2cd09e2 100644
(Continue reading)

Francisco Soto | 4 Nov 2009 20:41
Picon

Fwd: Help please


Hello:

     My name is Francisco Soto, I'm working in a project for the university, and I want to use Kdevelop. This is my first time using the program, and I try to make the clasical test, "hello world" in the link http://www.estrellateyarde.es/discover/manual-c-kdevelop-en-linux
     But when I run the program it says to me
....
....
*** Creating aclocal.m4
acinclude.m4:3724: the serial number must appear before any macro definition
acinclude.m4:3769: the serial number must appear before any macro definition
acinclude.m4:3814: the serial number must appear before any macro definition
acinclude.m4:6022: the serial number must appear before any macro definition
*** Creating configure
.....
.....
error finish state 1

     I can't find any help in forums or in http://www.kdevelop.org/
Can you tell me were I can find any help please.


Thank you very much.
If you don't have any information, please tell me, I don't want to wait an answer that will never came to me. Sorry for my english

Francisco Soto D.
Estudent in electronic engineer, Universidad Tecnica Federico Santa Maria



_______________________________________________
Bug-libtool mailing list
Bug-libtool <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool
Ralf Wildenhues | 4 Nov 2009 20:52
Picon
Picon

Re: Fwd: Help please

Hello Francisco,

* Francisco Soto wrote on Wed, Nov 04, 2009 at 08:41:55PM CET:
> I want to use Kdevelop. This is my first time using the program, and I
> try to make the clasical test, "hello world" in the link
> http://www.estrellateyarde.es/discover/manual-c-kdevelop-en-linux
>      But when I run the program it says to me
> ....
> ....
> *** Creating aclocal.m4
> acinclude.m4:3724: the serial number must appear before any macro definition
> acinclude.m4:3769: the serial number must appear before any macro definition
> acinclude.m4:3814: the serial number must appear before any macro definition
> acinclude.m4:6022: the serial number must appear before any macro definition

These are all just warnings.  They shouldn't cause an error.

> *** Creating configure
> .....
> .....
> error finish state 1

Hmm.  This error message presumably comes from kdevelop, but I guess
some part of the bootstrap/configure procedure failed.  Are there more
messages, can you cut and paste them all?

Thanks,
Ralf
Francisco Soto | 4 Nov 2009 21:00
Picon

Re: Fwd: Help please

Hello, thank for answer so fast
here is everithing



cd '/home/francisco/HolaMundo' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make -f Makefile.cvs && cd '/home/francisco/HolaMundo/debug' && CXXFLAGS="-O0 -g3" "/home/francisco/HolaMundo/configure" --enable-debug=full && cd '/home/francisco/HolaMundo/debug/./src' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" LC_MESSAGES="C" LC_CTYPE="C" make -k holamundo
This Makefile is only for the CVS repository
This will be deleted before making the distribution

*** automake (GNU automake) 1.10.1 found.
*** Creating acinclude.m4
*** Creating list of subdirectories
cd . && make -f admin/Makefile.common subdirs
*** Creating configure.files
*** Creating configure.in
cd . && make -f admin/Makefile.common configure.in ;
*** Creating aclocal.m4
acinclude.m4:3724: the serial number must appear before any macro definition
acinclude.m4:3769: the serial number must appear before any macro definition
acinclude.m4:3814: the serial number must appear before any macro definition
acinclude.m4:6022: the serial number must appear before any macro definition
*** Creating configure
*** Creating config.h template
*** Creating Makefile templates
*** Postprocessing Makefile templates
*** Creating date/time stamp
*** Finished
Don't forget to run ./configure
If you haven't done so in a while, run ./configure --help
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
instalando -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for kde-config... /usr/bin/kde-config
checking where to install... /usr (as returned by kde-config)
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether gcc is blacklisted... no
checking whether g++ supports -fno-builtin... yes
checking whether g++ supports -Woverloaded-virtual... yes
checking whether g++ supports -Wmissing-format-attribute... yes
checking whether gcc supports -Wmissing-format-attribute... yes
checking whether g++ supports -Wundef... yes
checking whether g++ supports -Wno-long-long... yes
checking whether g++ supports -Wno-non-virtual-dtor... yes
checking whether g++ supports -fno-reorder-blocks... yes
checking whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fno-common... yes
checking whether g++ supports -fexceptions... yes
checking whether system headers can cope with -O2 -fno-inline... irrelevant
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -O0... yes
checking whether g++ supports -Wl,--no-undefined... yes
checking whether g++ supports -Wl,--allow-shlib-undefined... yes
not using lib directory suffix
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
enlazando file.o... (gcc)
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
enlazando file.o... (g++)
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for shl_load... (cached) no
checking for shl_load in -ldld... (cached) no
checking for dlopen... (cached) no
checking for dlopen in -ldl... (cached) yes
checking whether a program can dlopen itself... (cached) yes
checking whether a statically linked program can dlopen itself... (cached) yes
appending configuration tag "F77" to libtool
checking for msgfmt... msgfmt
checking for gmsgfmt... msgfmt
found msgfmt program is not GNU msgfmt; ignore it
checking for xgettext... :
checking for pkg-config... /usr/bin/pkg-config
checking if C++ programs can be compiled... yes
checking for strlcat... no
checking if strlcat needs custom prototype... yes - in libkdefakes
checking for strlcpy... no
checking if strlcpy needs custom prototype... yes - in libkdefakes
checking for main in -lutil... yes
checking for main in -lcompat... no
checking for crypt in -lcrypt... yes
checking for socklen_t... yes
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for inet_ntoa... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for sys/types.h... (cached) yes
checking for stdint.h... (cached) yes
checking sys/bitypes.h usability... yes
checking sys/bitypes.h presence... yes
checking for sys/bitypes.h... yes
checking for poll in -lpoll... no
checking Carbon/Carbon.h usability... no
checking Carbon/Carbon.h presence... no
checking for Carbon/Carbon.h... no
checking CoreAudio/CoreAudio.h usability... no
checking CoreAudio/CoreAudio.h presence... no
checking for CoreAudio/CoreAudio.h... no
checking if res_init needs -lresolv... yes
checking for res_init... yes
checking if res_init needs custom prototype... no
checking for killpg in -lucb... no
checking for int... yes
checking size of int... 4
checking for short... yes
checking size of short... 2
checking for long... yes
checking size of long... 4
checking for char *... yes
checking size of char *... 4
checking for dlopen in -ldl... (cached) yes
checking for shl_unload in -ldld... no
checking for size_t... yes
checking size of size_t... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking sizeof size_t == sizeof unsigned long... yes
checking for PIE support... yes
checking if enabling -pie/fPIE support... yes
checking crt_externs.h usability... no
checking crt_externs.h presence... no
checking for crt_externs.h... no
checking for _NSGetEnviron... no
checking for vsnprintf... yes
checking for snprintf... yes
checking for X... libraries /usr/lib, headers .
checking for IceConnectionNumber in -lICE... yes
checking for libXext... yes
checking for pthread_create in -lpthread... yes
checking for extra includes... no
checking for extra libs... no
checking for libz... -lz
checking for libpng... -lpng -lz -lm
checking for libjpeg6b... no
checking for libjpeg... -ljpeg
checking for perl... /usr/bin/perl
configure: error: Qt (>= Qt 3.2 and < 4.0) (headers and libraries) not found. Please check your installation!
For more details about this problem, look at the end of config.log.
checking for Qt...
***Terminado con estado 1***







2009/11/4 Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de>
Hello Francisco,

* Francisco Soto wrote on Wed, Nov 04, 2009 at 08:41:55PM CET:
> I want to use Kdevelop. This is my first time using the program, and I
> try to make the clasical test, "hello world" in the link
> http://www.estrellateyarde.es/discover/manual-c-kdevelop-en-linux
>      But when I run the program it says to me
> ....
> ....
> *** Creating aclocal.m4
> acinclude.m4:3724: the serial number must appear before any macro definition
> acinclude.m4:3769: the serial number must appear before any macro definition
> acinclude.m4:3814: the serial number must appear before any macro definition
> acinclude.m4:6022: the serial number must appear before any macro definition

These are all just warnings.  They shouldn't cause an error.

> *** Creating configure
> .....
> .....
> error finish state 1

Hmm.  This error message presumably comes from kdevelop, but I guess
some part of the bootstrap/configure procedure failed.  Are there more
messages, can you cut and paste them all?

Thanks,
Ralf

_______________________________________________
Bug-libtool mailing list
Bug-libtool <at> gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool

Gmane