Hi Vadim! If you want to try a static libc, which should fix this, do
this in linux.defs:
# under redhat 6.1 and slackware 7.0 we needed to have this
# link be static, but should be ok with the fix to unixport/rsym_elf.c
LDCC=${CC} -static
###### comment this out for static libc link ###### LDCC=${CC}
ldd on the binary should indicate that all libs are statically linked
in.
I'd be interested to know of the details of your experience here. We
will doubtlessly have to bring this up with the emacs people.
I'm assuming you are doing the 'traditional' maxima gcl build,
i.e. doing the save-system after the .o files have been loaded. This
should be fine given your description of the problem. But just to let
you know, there is an --enable-gcl-altlink option to the maxima
configure, which will effectively use ld to link in the .o files into
raw_maxima via compiler::link, and then run the interpreted maxima
init code, and save the system at this later stage. This is required
on machines where GCL currently cannot relocate .o files into the
running image (mips(el), hppa, ia64, and alpha), but can be run
anywhere. Doesn't sound like you need this though.
Take care,
"Vadim V. Zhytnikov" <address@hidden> writes:
I'm trying to build Maxima with GCL 2.5.3 in such a way
to make it work on any rpm-based linux distro with
i586 cpu or greater. Unfortunately I hit the problem
which Camm described recently - resulting Maxima binaries
segfaults if I run them on the system with glibc version
different from build host glibc. Strange thing is that
GCL itself works fine, but Maxima build on the top of
this GCL crashes.
What might be the cure? Will static GCL build help?
I already linked all other libraries (libreadline, libncurses)
statically but I don't know how to build GCL
statically with glibc.
Any help is greatly appreciated. I wrote the paper about
Maxima for Russian computer journal and this binaries
are intended to be included on the attached CD-ROM.
I have to produce them in two days :(
I also noticed that if I configure GCL with
given --build=... --host=... and --enable-locbfd
then gmp subconfigure respects the --host but
libbfd ignores it. Is this correct?
--
Vadim V. Zhytnikov
<address@hidden>
<address@hidden>
_______________________________________________
Gcl-devel mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/gcl-devel