Re: atlas, lapack on arm
Greetings, and thanks for your reply!
Philip Blundell <firstname.lastname@example.org> writes:
> On Sat, 2002-02-23 at 21:37, Camm Maguire wrote:
> > ../../tmglib_LINUX.a(slatms.o): In function `slatms_':
> > slatms.o(.text+0x974): undefined reference to `.LC12'
> > slatms.o(.text+0x97c): undefined reference to `.LC14'
> > slatms.o(.text+0xda4): undefined reference to `.LC12'
> > slatms.o(.text+0xdac): undefined reference to `.LC15'
> > slatms.o(.text+0x1314): undefined reference to `.LC15'
> > slatms.o(.text+0x1834): undefined reference to `.LC15'
> > slatms.o(.text+0x1d00): undefined reference to `.LC12'
> > slatms.o(.text+0x1d08): undefined reference to `.LC15'
> > Here libblas and liblapack are shared libs. One can build an
> > executable without PIC and then link to a PIC shared lib on arm,
> > right?
> Right. The errors above are caused by a compiler bug. Try using
> g77-3.0 rather than the default 2.95. If that doesn't work, you will
> need to generate a testcase and file a bug against g77.
I've tried to use the -3.0 compilers as a user on rameau, the only arm
available to us AFAICT, but the installed libc won't take it. In
other words, I do a 'dpkg --fsys-tarfile' on the debs, setup links in
$HOME/usr/bim, export PAtH=$HOME/usr/bin:$PATH, export
GCC_EXEC_PREFIX=$HOME/usr/lib/gcc-lib/, and then gcc(-3.0) -v gives me
a libc shared lib loading error. I can do this on other debian
machines without problem.
What can I do here?
> > 2) atlas: Atlas times various routines to pick the most efficient
> > for the host in question. All timings on arm are so varied that
> > the build fails being unable to get timing values within the
> > required precision.
> I've no idea what's going on here. I'll try compiling it by hand and
> see what happens.
Great! Please let me know.
Camm Maguire email@example.com
"The earth is but one country, and mankind its citizens." -- Baha'u'llah