Bug#344662: libtool: gentoo patch breaking on Debian amd64
On Fri, Jan 13, 2006 at 04:07:18AM -0500, Mike Frysinger wrote: sorry guys, i missed this e-mail since it was cc-ed to the libtool list and my filters ate it :) so what's the story with this patch ? is it the cause of the Debian bug 344662 ? reading the report it doesnt seem like it is ... As far as I can tell the patch in question does cause problems. i'm pretty sure we took libtool-1.4.2-multilib.patch from mandrake, but i cant say for sure as it's been in portage since before i joined Gentoo ... unrelated to your e-mail, i had already removed applying it with our 1.5.22 libtool ebuild in my effort to cut out all extraneous libtool patches by either labeling them obsolete or sending them upstream ... That would be good news. I'm also going to request that the Debian sysfs package no longer ships the .la file since it's clearly unsupported. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344662: libtool: gentoo patch breaking on Debian amd64
On Fri, January 13, 2006 12:33 pm, Kurt Roeckx said: On Fri, Jan 13, 2006 at 04:07:18AM -0500, Mike Frysinger wrote: [...] I'm also going to request that the Debian sysfs package no longer ships the .la file since it's clearly unsupported. I already pointed libsysfs maintainer to this bug and it would be nice to apply those changes before the libsysfs2 transition as with the latter libcpufreq is linking statically on x86 too (but succesfully). See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347630 Kurt: really thanks for your help here ! -- mattia :wq!
Bug#344662: libtool: gentoo patch breaking on Debian amd64.
Hi Kurt, * Kurt Roeckx wrote on Wed, Dec 28, 2005 at 02:36:07PM CET: On Wed, Dec 28, 2005 at 10:03:55AM +0100, Ralf Wildenhues wrote: Since I don't have a Debian amd64 system for testing, please rerun the build, post the ./libtool --mode=link command, and all of its output, with --debug added. Please also post /bin/sh ./libtool --mode=link --debug x86_64-linux-gnu-gcc -Wall -Wall -g -O2 -lsysfs -o libcpufreq.la -rpath /usr/lib -version-info 0:0:0 -lsysfs cpufreq.lo sysfs.lo proc.lo See libtool.debug attachment. ./libtool --config See libtool.config attachment. I've also attached the /usr/lib/libsysfs.la file. Thanks. Note that the shared library is installed in /lib, but the rest are in /usr/lib. 1) This is a bug, but not the one you reported. It's not supported by libtool to install the .la file in a different location than the actual shared (or static) library. Probably the easiest workaround would be to not install the .la file at all in this case. It may just happen to work (in case all of the files end up in default-searched paths), but it's not supported. 2) You are right in that the gentoo-specific patch hurts for Debian. Does Debian amd64 have a symlink /lib64 - /lib? Without it I can't see why it would get to the link line at all. Cheers, Ralf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#344662: libtool: gentoo patch breaking on Debian amd64.
On Wed, Dec 28, 2005 at 10:03:55AM +0100, Ralf Wildenhues wrote: Hi Kurt, I'm not really sure why this breaks anything though. My guess would be that you're removing paths it needs. I'm not convinced yet that this is the cause for the breakage. It may well be, though. In any case, it's a system-specific patch; it was not accepted into GNU libtool simply because it's not valid for all GNU/Linux distributions. Don't blame libtool for their non-uniformity. Since I don't have a Debian amd64 system for testing, please rerun the build, post the ./libtool --mode=link command, and all of its output, with --debug added. Please also post /bin/sh ./libtool --mode=link --debug x86_64-linux-gnu-gcc -Wall -Wall -g -O2 -lsysfs -o libcpufreq.la -rpath /usr/lib -version-info 0:0:0 -lsysfs cpufreq.lo sysfs.lo proc.lo See libtool.debug attachment. ./libtool --config See libtool.config attachment. I've also attached the /usr/lib/libsysfs.la file. Note that the shared library is installed in /lib, but the rest are in /usr/lib. I assume that I can get the source of the corresponding package (the exact one please!) from these URLs, right? http://ftp.debian.org/debian/pool/main/c/cpufrequtils/cpufrequtils_0.4.orig.tar.gz http://ftp.debian.org/debian/pool/main/c/cpufrequtils/cpufrequtils_0.4-1.diff.gz Yes, those are the correct files. Kurt libtool: enabling shell trace mode + preserve_args=' --debug' + test 16 -gt 0 + arg=x86_64-linux-gnu-gcc + shift + case $arg in + optarg= + test -n '' + case $arg in + nonopt=x86_64-linux-gnu-gcc + break + test -n '' + exec_cmd= + test -z '' + test -z link + test -n '' + generic_help='Try `libtool --help'\'' for more information.' + help='Try `libtool --help --mode=link'\'' for more information.' + case $mode in + modename='libtool: link' + case $host in + allow_undefined=yes + libtool_args=x86_64-linux-gnu-gcc + base_compile='x86_64-linux-gnu-gcc -Wall -Wall -g -O2 -lsysfs -o libcpufreq.la -rpath /usr/lib -version-info 0:0:0 -lsysfs cpufreq.lo sysfs.lo proc.lo' + compile_command=x86_64-linux-gnu-gcc + finalize_command=x86_64-linux-gnu-gcc + compile_rpath= + finalize_rpath= + compile_shlibpath= + finalize_shlibpath= + convenience= + old_convenience= + deplibs= + old_deplibs= + compiler_flags= + linker_flags= + dllsearchpath= ++ pwd + lib_search_path=/usr/src/cpufrequtils-0.4/libcpufreq + inst_prefix_dir= + avoid_version=no + dlfiles= + dlprefiles= + dlself=no + export_dynamic=no + export_symbols= + export_symbols_regex= + generated= + libobjs= + ltlibs= + module=no + no_install=no + objs= + non_pic_objects= + precious_files_regex= + prefer_static_libs=no + preload=no + prev= + prevarg= + release= + rpath= + xrpath= + perm_rpath= + temp_rpath= + thread_safe=no + vinfo= + vinfo_number=no + func_infer_tag x86_64-linux-gnu-gcc -Wall -Wall -g -O2 -lsysfs -o libcpufreq.la -rpath /usr/lib -version-info 0:0:0 -lsysfs cpufreq.lo sysfs.lo proc.lo + test -n ' CXX' + test -z '' + CC_quoted= + for arg in '$CC' + case $arg in + CC_quoted=' x86_64-linux-gnu-gcc' + case $@ in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + for arg in '$@' + case $arg in + test -n '' + test 15 -gt 0 + arg=-Wall + shift + case $arg in + qarg=-Wall + libtool_args='x86_64-linux-gnu-gcc -Wall' + test -n '' + prevarg=-Wall + case $arg in ++ echo X-Wall ++ /bin/sed -e '1s/^X//' -e 's/\([\\`\\$]\)/\\\1/g' + arg=-Wall + case $arg in + test -n -Wall + compile_command='x86_64-linux-gnu-gcc -Wall' + finalize_command='x86_64-linux-gnu-gcc -Wall' + test 14 -gt 0 + arg=-Wall + shift + case $arg in + qarg=-Wall + libtool_args='x86_64-linux-gnu-gcc -Wall -Wall' + test -n '' + prevarg=-Wall + case $arg in ++ echo X-Wall ++ /bin/sed -e '1s/^X//' -e 's/\([\\`\\$]\)/\\\1/g' + arg=-Wall + case $arg in + test -n -Wall + compile_command='x86_64-linux-gnu-gcc -Wall -Wall' + finalize_command='x86_64-linux-gnu-gcc -Wall -Wall' + test 13 -gt 0 + arg=-g + shift + case $arg in + qarg=-g + libtool_args='x86_64-linux-gnu-gcc -Wall -Wall -g' + test -n '' + prevarg=-g + case $arg in ++ echo X-g ++ /bin/sed -e '1s/^X//' -e 's/\([\\`\\$]\)/\\\1/g' + arg=-g + case $arg in + test -n -g + compile_command='x86_64-linux-gnu-gcc -Wall -Wall -g' + finalize_command='x86_64-linux-gnu-gcc -Wall -Wall -g' + test 12 -gt 0 + arg=-O2 + shift + case $arg in + qarg=-O2 + libtool_args='x86_64-linux-gnu-gcc -Wall -Wall -g -O2' + test -n '' + prevarg=-O2 + case $arg in ++ echo X-O2 ++ /bin/sed -e '1s/^X//' -e 's/\([\\`\\$]\)/\\\1/g' + arg=-O2 + case $arg in + test -n -O2 +
