Closed GoogleCodeExporter closed 8 years ago
I've also attempted to set the configure flag of --libdir=/usr/lib64 and it
still
gives the same error.
Original comment by sglaf...@gmail.com
on 12 Jun 2007 at 1:01
Do you have a 64bit version of GTK+ 2.x installed?
Original comment by akira.ta...@gmail.com
on 17 Jul 2007 at 4:06
[deleted comment]
[sam@ ~]$ rpm -qa | grep gtk+
libgtk+-x11-2.0_0-2.10.3-4mdv2007.0
libgtk+2.0_0-devel-2.10.3-4mdv2007.0
lib64gtk+2.0_0-2.10.3-5.3mdv2007.0
lib64gtk+-x11-2.0_0-2.10.3-5.3mdv2007.0
libgtk+1.2-devel-1.2.10-45mdv2007.0
lib64gtk+1.2-devel-1.2.10-45mdv2007.0
libgtk+2.0_0-2.10.3-4mdv2007.0
lib64gtk+2.0_0-devel-2.10.3-5.3mdv2007.0
gtk+2.0-2.10.3-5.3mdv2007.0
libgtk+1.2-1.2.10-45mdv2007.0
lib64gtk+1.2-1.2.10-45mdv2007.0
Original comment by sglaf...@gmail.com
on 19 Jul 2007 at 2:37
Thanks. can you provide the logs around where the error happened, including
what the
kind of parameters are given to gcc? and what about gcc -v or whatever the C
compiler
used for building?
Actually I can build gconf-cleaner-0.0.2 on Fedora 7 x86_64 box without any
problems BTW.
Original comment by akira.ta...@gmail.com
on 19 Jul 2007 at 5:42
[sam@~ ]$ gcc -v
Using built-in specs.
Target: x86_64-mandriva-linux-gnu
Configured with: ../configure --prefix=/usr --libexecdir=/usr/lib
--with-slibdir=/lib64 --mandir=/usr/share/man --infodir=/usr/share/info
--enable-shared --enable-threads=posix --enable-checking=release
--enable-languages=c,c++,ada,fortran,objc,obj-c++,java
--host=x86_64-mandriva-linux-gnu --with-cpu=generic --with-system-zlib
--enable-long-long --enable-__cxa_atexit --enable-clocale=gnu
--disable-libunwind-exceptions --enable-java-awt=gtk
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --enable-gtk-cairo
--enable-ssp --disable-libssp
Thread model: posix
gcc version 4.1.1 20060724 (prerelease) (4.1.1-3mdk)
Original comment by sglaf...@gmail.com
on 23 Jul 2007 at 6:04
Thanks. it looks like a libtool bug. if you have libtool 1.5.24 installed, what
happens after libtoolize --force --copy and build again? (perhaps you may be
required
to do run automake and autoconf manually if make doesn't do that)
Original comment by akira.ta...@gmail.com
on 24 Jul 2007 at 5:47
[sam@~ gconf-cleaner-0.0.2]$ libtoolize --force --copy
libtoolize: `/usr/share/aclocal/libtool.m4' is serial 47, less than 48 in
`aclocal.m4'
To remain compatible, you should update your `aclocal.m4' by running aclocal.
[sam@vader gconf-cleaner-0.0.2]$ su
Password:
[root@~ gconf-cleaner-0.0.2]# aclocal
/usr/share/aclocal/libguppi.m4:11: warning: underquoted definition of
AM_PATH_LIBGUPPI
run info '(automake1.8)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/libfame.m4:6: warning: underquoted definition of
AM_PATH_LIBFAME
/usr/share/aclocal/frontline.m4:7: warning: underquoted definition of
AM_PATH_FRONTLINE
Original comment by sglaf...@gmail.com
on 26 Jul 2007 at 1:34
After running the suggested command, I tried to rebuild with the same results.
Do
you think I need to update my libtool? I have:
[root@~ gconf-cleaner-0.0.2]# rpm -qa | grep libtool
libtool-base-1.5.20-9mdv2007.0
libtool-1.5.20-9mdv2007.0
Original comment by sglaf...@gmail.com
on 26 Jul 2007 at 1:41
My bad - I re-ran your command as root. Trying again to recompile.
Original comment by sglaf...@gmail.com
on 26 Jul 2007 at 1:42
Re-ran configure and make as root after the libtoolize command and the compile
failed
again. I've attached my output.
Original comment by sglaf...@gmail.com
on 26 Jul 2007 at 1:47
Attachments:
Well, if it's possible, yes. actually 1.5.20 was what originally gconf-cleaner
0.0.2
used. so it shouldn't makes any changes. or I can put the testing package so
that I'd
like to fix this issue in next release.
Thanks,
Original comment by akira.ta...@gmail.com
on 26 Jul 2007 at 3:07
Sorry for not getting back to you earlier. an attached tarball is made with
libtool
1.5.24. please let me know how it is.
Original comment by akira.ta...@gmail.com
on 31 Jul 2007 at 11:20
Attachments:
This lastest package worked perfectly for me. I was able to configure, make and
install without a hitch. I've attached the output.
Original comment by sglaf...@gmail.com
on 1 Aug 2007 at 1:13
Attachments:
Thank you for confirmation. will push the latest release officially then.
Original comment by akira.ta...@gmail.com
on 2 Aug 2007 at 12:16
Original issue reported on code.google.com by
sglaf...@gmail.com
on 12 Jun 2007 at 12:55