Debug help on x86_64

Quentin Spencer qspencer at ieee.org
Wed Jun 22 17:46:59 UTC 2005


Earlier, I wrote:

>I got an error trying to build octave-forge on x86_64 (the other archs
>worked fine), and not having access to the necessary hardware, I'm not
>sure how to debug it. It happens when configure is looking for
>mkoctfile, a script in octave-devel that compiles dynamically loadable
>functions for octave. The error I get is:
>
>checking for mkoctfile... mkoctfile
>/usr/bin/ld: cannot find -loctinterp
>collect2: ld returned 1 exit status
>configure: error: Could not run mkoctfile
>error: Bad exit status from /var/tmp/rpm-tmp.65687 (%build)
>
>So, it seems that mkoctfile is looking for libraries in the wrong place
>on x86_64. This may be something I need to correct in octave itself, but
>I'm not sure. Ideas?
>
>-Quentin
>  
>

OK, it looks like the problem is that mkoctfile is looking in /usr/lib
instead of /usr/lib64. I think this is fixed by adding
--libdir=%{_libdir} to the configure command. Can anyone verify that
%{_libdir} on x86_64 returns /usr/lib64?

-Quentin




More information about the fedora-extras-list mailing list