3.4.1 - 'mabshoff' hard-coded in 'linbox'

0 views
Skip to first unread message

Dr. David Kirkby

unread,
Apr 25, 2009, 2:04:15 AM4/25/09
to sage-...@googlegroups.com
I've tried to build 3.4.1 on Sun Blade 2000 (SPARC) workstation, using
the tool chain I downloaded from the Sage web site (based on gcc 4.3.2).

This went well for several hours, but then failed. It appears the
directory /home/mabshoff/sparc-solaris-toolchain/ is hard-coded
somewhere, so naturally fails if the build-directory is elsewhere:

The two critical lines in the output are:

----------------
grep: can't open /home/mabshoff/sparc-solaris-toolchain//lib/libstdc++.la
/opt/csw/bin/gsed: can't read
/home/mabshoff/sparc-solaris-toolchain//lib/libstd c++.la: No such file
or directory
libtool: link:
`/home/mabshoff/sparc-solaris-toolchain//lib/libstdc++.la' is not a
valid libtool archive
------------------

As you can see, 'mabshoff' must be hard-coded somewhere. Since the
compilation aborted, I'll try to start it again by making a link from
/ex/port/home/drkirkby to /home/mabshof

Here is more of the output:


.. -I../.. -I../../linbox -g
-I"/export/home/drkirkby/sage/sage-3.4.1/local/inc lude/linbox"
-I"/export/home/drkirkby/sage/sage-3.4.1/local"/include -g -fPIC -
I"/export/home/drkirkby/sage/sage-3.4.1/local/include"
-I"/export/home/drkirkby/ sage/sage-3.4.1/local/include/linbox"
-L"/export/home/drkirkby/sage/sage-3.4.1/ local/lib"
-I/export/home/drkirkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6/src -
I/export/home/drkirkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6/src/linbox
-I/ex port/home/drkirkby/sage/sage-3.4.1/local/include
-I/export/home/drkirkby/sage/s age-3.4.1/local/include
-D__LINBOX_HAVE_CBLAS -c -o debug.lo debug.C
g++ -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../linbox -g
-I/export/home/drkirk by/sage/sage-3.4.1/local/include/linbox
-I/export/home/drkirkby/sage/sage-3.4.1/ local/include -g -fPIC
-I/export/home/drkirkby/sage/sage-3.4.1/local/include -I/
export/home/drkirkby/sage/sage-3.4.1/local/include/linbox
-L/export/home/drkirkb y/sage/sage-3.4.1/local/lib
-I/export/home/drkirkby/sage/sage-3.4.1/spkg/build/l inbox-1.1.6/src
-I/export/home/drkirkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6/
src/linbox -I/export/home/drkirkby/sage/sage-3.4.1/local/include
-I/export/home/ drkirkby/sage/sage-3.4.1/local/include
-D__LINBOX_HAVE_CBLAS -c debug.C -fPIC - DPIC -o .libs/debug.o
/bin/bash ../../libtool --tag=CXX --mode=link g++ -g -fPIC
-I"/export/home/dr kirkby/sage/sage-3.4.1/local/include"
-I"/export/home/drkirkby/sage/sage-3.4.1/l ocal/include/linbox"
-L"/export/home/drkirkby/sage/sage-3.4.1/local/lib" -I/exp
ort/home/drkirkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6/src
-I/export/home/drk
irkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6/src/linbox
-I/export/home/drkirkb y/sage/sage-3.4.1/local/include
-I/export/home/drkirkby/sage/sage-3.4.1/local/i nclude
-D__LINBOX_HAVE_CBLAS -o libutil.la timer.lo error.lo commentator.lo
d ebug.lo -lcblas -latlas
-L/export/home/drkirkby/sage/sage-3.4.1/local/lib -lgmp xx -lgmp
-L/export/home/drkirkby/sage/sage-3.4.1/local/lib -lgivaro
grep: can't open /home/mabshoff/sparc-solaris-toolchain//lib/libstdc++.la
/opt/csw/bin/gsed: can't read
/home/mabshoff/sparc-solaris-toolchain//lib/libstd c++.la: No such file
or directory
libtool: link:
`/home/mabshoff/sparc-solaris-toolchain//lib/libstdc++.la' is not a
valid libtool archive
make[6]: *** [libutil.la] Error 1
make[6]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin
box-1.1.6/src/linbox/util'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin
box-1.1.6/src/linbox/util'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin box-1.1.6/src/linbox'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin box-1.1.6/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin box-1.1.6/src'
Error building linbox
make[2]: Entering directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/li nbox-1.1.6/src'
Making install in linbox
make[3]: Entering directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/li nbox-1.1.6/src/linbox'
Making install in util
make[4]: Entering directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/li
nbox-1.1.6/src/linbox/util'
Making install in formats
make[5]: Entering directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/li
nbox-1.1.6/src/linbox/util/formats'
make[6]: Entering directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/li
nbox-1.1.6/src/linbox/util/formats'
make[6]: Nothing to be done for `install-exec-am'.
test -z
"/export/home/drkirkby/sage/sage-3.4.1/local/include/linbox/util/formats
" || /export/home/drkirkby/sparc-solaris-toolchain/bin/mkdir -p
"/export/home/dr kirkby/sage/sage-3.4.1/local/include/linbox/util/formats"
/export/home/drkirkby/sparc-solaris-toolchain/bin/install -c -m 644
'generic-de nse.h'
'/export/home/drkirkby/sage/sage-3.4.1/local/include/linbox/util/formats/
generic-dense.h'
/export/home/drkirkby/sparc-solaris-toolchain/bin/install -c -m 644
'maple.h' '
/export/home/drkirkby/sage/sage-3.4.1/local/include/linbox/util/formats/maple.h'
/export/home/drkirkby/sparc-solaris-toolchain/bin/install -c -m 644
'matrix-mar ket.h'
'/export/home/drkirkby/sage/sage-3.4.1/local/include/linbox/util/formats/
matrix-market.h'
/export/home/drkirkby/sparc-solaris-toolchain/bin/install -c -m 644
'sms.h' '/e
xport/home/drkirkby/sage/sage-3.4.1/local/include/linbox/util/formats/sms.h'
/export/home/drkirkby/sparc-solaris-toolchain/bin/install -c -m 644
'matrix-str eam-readers.h'
'/export/home/drkirkby/sage/sage-3.4.1/local/include/linbox/util/
formats/matrix-stream-readers.h'
/export/home/drkirkby/sparc-solaris-toolchain/bin/install -c -m 644
'sparse-row .h'
'/export/home/drkirkby/sage/sage-3.4.1/local/include/linbox/util/formats/spa
rse-row.h'
make[6]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin
box-1.1.6/src/linbox/util/formats'
make[5]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin
box-1.1.6/src/linbox/util/formats'
make[5]: Entering directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/li
nbox-1.1.6/src/linbox/util'
/bin/bash ../../libtool --tag=CXX --mode=link g++ -g -fPIC
-I"/export/home/dr kirkby/sage/sage-3.4.1/local/include"
-I"/export/home/drkirkby/sage/sage-3.4.1/l ocal/include/linbox"
-L"/export/home/drkirkby/sage/sage-3.4.1/local/lib" -I/exp
ort/home/drkirkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6/src
-I/export/home/drk
irkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6/src/linbox
-I/export/home/drkirkb y/sage/sage-3.4.1/local/include
-I/export/home/drkirkby/sage/sage-3.4.1/local/i nclude
-D__LINBOX_HAVE_CBLAS -o libutil.la timer.lo error.lo commentator.lo
d ebug.lo -lcblas -latlas
-L/export/home/drkirkby/sage/sage-3.4.1/local/lib -lgmp xx -lgmp
-L/export/home/drkirkby/sage/sage-3.4.1/local/lib -lgivaro
grep: can't open /home/mabshoff/sparc-solaris-toolchain//lib/libstdc++.la
/opt/csw/bin/gsed: can't read
/home/mabshoff/sparc-solaris-toolchain//lib/libstd c++.la: No such file
or directory
libtool: link:
`/home/mabshoff/sparc-solaris-toolchain//lib/libstdc++.la' is not a
valid libtool archive
make[5]: *** [libutil.la] Error 1
make[5]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin
box-1.1.6/src/linbox/util'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin
box-1.1.6/src/linbox/util'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin box-1.1.6/src/linbox'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/export/home/drkirkby/sage/sage-3.4.1/spkg/build/lin box-1.1.6/src'
Error installing linbox

real 25m3.439s
user 19m22.491s
sys 0m42.040s
sage: An error occurred while installing linbox-1.1.6
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /export/home/drkirkby/sage/sage-3.4.1/install.log. Describe your
computer, o perating system, etc.
If you want to try to fix the problem, yourself *don't* just cd to
/export/home/drkirkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6 and type
'make'.
Instead type "/export/home/drkirkby/sage/sage-3.4.1/sage -sh"
in order to set all environment variables correctly, then cd to
/export/home/drkirkby/sage/sage-3.4.1/spkg/build/linbox-1.1.6
(When you are done debugging, you can type "exit" to leave the
subshell.)
make[1]: *** [installed/linbox-1.1.6] Error 1
make[1]: Leaving directory `/export/home/drkirkby/sage/sage-3.4.1/spkg'

real 25:09.4
user 19:17.8
sys 25.0
python: can't open file
'/export/home/drkirkby/sage/sage-3.4.1/devel/sage/doc/co
mmon/builder.py': [Errno 2] No such file or directory

mabshoff

unread,
Apr 25, 2009, 2:15:20 AM4/25/09
to sage-devel


On Apr 24, 11:04 pm, "Dr. David Kirkby" <david.kir...@onetel.net>
wrote:

Hi David,

> I've tried to build 3.4.1 on Sun Blade 2000 (SPARC) workstation, using
> the tool chain I downloaded from the Sage web site (based on gcc 4.3.2).
>
> This went well for several hours, but then failed. It appears the
> directory /home/mabshoff/sparc-solaris-toolchain/ is hard-coded
> somewhere, so naturally fails if the build-directory is elsewhere:

Find lib/libstdc++.la in the toolchain directory and fix the path. You
might want to look for other libtool generated files (i.e. various .la
files) in the toolchain directory and adjust accordingly. Normally you
should be able to delete them since libtool usually is clever enough
to deal with their absence.

The "hard coded path in libtool generated file problem" is something
we do fix for Sage also, so unfortunately for now this will remain
broken of now until we fix, even though I am blaming LinBox's build
system for this error since it shouldn't fail out. I assume you set
LD_LIBRARY_PATH correctly so that libstdc++.so is found. Many crappy
projects link libstdc++ for some dumb reasons when it isn't required,
i.e. if you compile and link code with g++ you should never explicitly
link it. Oh well ...

Cheers,

Michael

Tom Boothby

unread,
Apr 25, 2009, 2:59:20 AM4/25/09
to sage-...@googlegroups.com
If I hard-code mabshoff into my programs, will they build more
reliably on more systems, and leak less memory?
Reply all
Reply to author
Forward
0 new messages