[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: matlab 5.3 seg fault (can it use both libc.so.6 & libc.so.5 ?)



Aaron

See if you can get the libdl, libXt, libX11, libXpm, libSM, libICE and
ld-linux libs that MATHWORKS compiled the MATLAB binary against and stick 
them in one of the Matlab 5.3 directories, probably
/usr/local/matlab5.3/sys/os/lnx86, listed below in your ldd output. 
The libs that it is currently pulling in are compiled against libc6 and
that is why it is pulling in libc6 as well.  Ask them to stick all the
required libs on there ftp site somewhere(as I am sure others will have
the problem as well), they currently have all the libs for 5.2 at 
ftp://ftp.mathworks.com/pub/tech-support/outgoing/linux/matlab5.

This is what I have for my copy of 5.2:

>> !ldd /usr/local/matlab5/bin/lnx86/matlab
        libXpm.so.4 => /usr/local/matlab5/sys/lnx86/libXpm.so.4 (0x4000b000)
        libXt.so.6 => /usr/local/matlab5/sys/lnx86/libXt.so.6 (0x40019000)
        libXext.so.6 => /usr/local/matlab5/sys/lnx86/libXext.so.6 (0x4005b000)
        libX11.so.6 => /usr/local/matlab5/sys/lnx86/libX11.so.6 (0x40064000)
        libtermcap.so.2 => /lib/libtermcap.so.2 (0x400e1000)
        libdl.so.1 => /usr/local/matlab5/sys/lnx86/libdl.so.1 (0x400e5000)
        libg++.so.27 => /usr/local/matlab5/sys/lnx86/libg++.so.27 (0x400e8000)
        libstdc++.so.27 => /usr/local/matlab5/sys/lnx86/libstdc++.so.27 (0x40120
000)
        libm.so.5 => /usr/local/matlab5/sys/lnx86/libm.so.5 (0x40152000)
        libc.so.5 => /usr/local/matlab5/sys/lnx86/libc.so.5 (0x4015b000)
        libSM.so.6 => /usr/local/matlab5/sys/lnx86/libSM.so.6 (0x40217000)
        libICE.so.6 => /usr/local/matlab5/sys/lnx86/libICE.so.6 (0x40220000)

Notice that all libs(except termcap) are in my matlab tree.

-- 
Brian 
---------------------------------------------------------------------
"Never criticize anybody until you have walked a mile in their shoes,  
 because by that time you will be a mile away and have their shoes." 
							   - unknown  

Mechanical Engineering                                bservis@usa.net
Purdue University                   http://www.ecn.purdue.edu/~servis
---------------------------------------------------------------------

*- On 14 Apr, amj@fhs.lawrence.ks.us wrote about "matlab 5.3 seg fault (can it use both libc.so.6 & libc.so.5 ?)"
> Hi all,
> 
> 	Mathworks tech support has been unable to help get matlab 5.3
> running on my Debian system.  I was wondering if anybody else has got
> it working and perhaps would know how to fix my problem.
> 
> When I start matlab is says,
> 
> 	Segmentation fault
> 
> BTW, the license manager appears to be up and running.
> 
> Here is an env variable that was used to find all the needed libs.
> 
> LD_LIBRARY_PATH=/usr/X11R6/lib/:/usr/local/matlab5.3/extern/lib/lnx86:/usr/local/matlab5.3/sys/os/lnx86/:/usr/local/matlab5.3/bin/lnx86
> 
> I suspect matlab is confused since it is finding libc.so.6, as well as
> libc.so.5 . Mathworks says they don't support libc6.  If this is the
> problem how would I, just for matlab ;-), "hide" the fact that libc6 is on
> my system?  How does it find /lib/libc.so.6 when it doesn't want it?
> 
> Commercial products linked against old libs are frustrating...
> 
> thank you for any help,
> aaron
> ----
> 
>> Dear Aaron:
>> 
>> I am writing in response to your email on April 12, 1999 regarding MATLAB
>> installation.
>> 
>> Thank you for sending me your information, there are a couple of things
>> that I noticed whcih may be causing the problem.
>> 
>> First, it seems as though /lib is missing from the Library path.  You can
>> add this to the path with the following command:
>> 
>> setenv LD_LIBRARY_PATH /lib/:$LD_LIBRARY_PATH
> 
> This is what I see for shared library linking.
> 
> ldd /usr/local/matlab5.3/bin/lnx86/matlab
>         libut.so => /usr/local/matlab5.3/extern/lib/lnx86/libut.so (0x4000b000)
>         libmwhardcopy.so => /usr/local/matlab5.3/bin/lnx86/libmwhardcopy.so (0x4002b000)
>         libmwhg.so => /usr/local/matlab5.3/bin/lnx86/libmwhg.so (0x4004f000)
>         libmwsimulink.so => /usr/local/matlab5.3/bin/lnx86/libmwsimulink.so (0x40149000)
>         libmwgui.so => /usr/local/matlab5.3/bin/lnx86/libmwgui.so (0x404ae000)
>         libmwnumerics.so => /usr/local/matlab5.3/bin/lnx86/libmwnumerics.so (0x40545000)
>         libmwmpath.so => /usr/local/matlab5.3/bin/lnx86/libmwmpath.so (0x405b3000)
>         libmwuix.so => /usr/local/matlab5.3/bin/lnx86/libmwuix.so (0x405c2000)
>         libmwcompiler.so => /usr/local/matlab5.3/bin/lnx86/libmwcompiler.so (0x40854000)
>         libmatlbmx.so => /usr/local/matlab5.3/bin/lnx86/libmatlbmx.so (0x408fa000)
>         libdl.so.1 => /lib/libdl.so.1 (0x40959000)
>         libg++.so.27 => /usr/local/matlab5.3/sys/os/lnx86/libg++.so.27 (0x4095c000)
>         libstdc++.so.27 => /usr/local/matlab5.3/sys/os/lnx86/libstdc++.so.27 (0x40990000)
>         libm.so.5 => /usr/local/matlab5.3/sys/os/lnx86/libm.so.5 (0x409bf000)
> ----->  libc.so.5 => /usr/local/matlab5.3/sys/os/lnx86/libc.so.5 (0x409c8000)
>         libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40a84000)
>         libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40ac7000)
>         libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x40b5f000)
>         libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40b6d000)
>         libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40b75000)
> ----->  libc.so.6 => /lib/libc.so.6 (0x40b89000)
>         ld-linux.so.2 => /lib/ld-linux.so.2 (0x40c2e000)
> 
>> I also noticed that the version of libc.so that you are using is version 6.
>>  Unfortunately, this version is not supported.  We are using revision 5.
> 
> matlab appears to find both libc.so.5 and libc.so.6 .  If it should
> not use libc.so.6 how do convice matlab not to see it?
> 
> 


Reply to: