[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gcmd-dev] build issue with rev. 2330 and libtool 2.2
From: |
Mamoru Tasaka |
Subject: |
[gcmd-dev] build issue with rev. 2330 and libtool 2.2 |
Date: |
Thu, 04 Dec 2008 17:50:41 +0900 |
User-agent: |
Thunderbird 2.0.0.18 (X11/20081119) |
Hello, all:
I tried to update gcmd to rev 2330 on Fedora rawhide (development tree),
however the build failed [1]
Now Fedora rawhide uses libtool 2.2.6. With this libtool
even after autogen.sh is called and configure is created, the file
"libtool" does not exist, so the following lines in configure.in
fails:
-----------------------------------------------------------
302 if /bin/sh ../libtool --mode=compile ${CC} $PYTHON_CFLAGS -c
testpython.c >/dev/null 2>&1 && \
303 /bin/sh ../libtool --mode=link ${CC} -o testpython.la -rpath
`pwd` -module -avoid-version $PYTHON_LIB_LOC testpython.lo $PYTHON_LIBS
$PYTHON_EXTRA_LIBS >/dev/null 2>&1 && \
304 grep 'dlname.*testpython' testpython.la >/dev/null 2>&1; then
305 result=yes
306 else
-----------------------------------------------------------
For now I apply the patch [2] to avoid using libtool in configure.
I would appreciate it if you would consider my patch.
[1] http://koji.fedoraproject.org/koji/getfile?taskID=973921&name=build.log
[2]
http://cvs.fedoraproject.org/viewvc/rpms/gnome-commander/devel/gnome-commander-1.2.8-trunk-libtool22.patch?revision=1.1
Regards,
Mamoru
- [gcmd-dev] build issue with rev. 2330 and libtool 2.2,
Mamoru Tasaka <=