On Mon, Mar 24, 2003 at 08:13:49AM +0200, [EMAIL PROTECTED] wrote:
> Hi,
> I intend to compile octave-2.1.44 on a celeron 600MHz running slackware
> 8.0 (kernel 2.2.xx, gcc 2.95). Most of the tools required by the package
> are compatible with my system, but it requires a newer version
> of the readline library (updated, without unpleasant
> side-effects) and gcc-3.2.2.
> I do not plan to replace the present compiler, as that might interfere
> with some of the other programs, but rather use hte new version for
> specific tasks.
> I need pointers to how to do it (preferably answering also the why
> questions).
> Specifically:
> I downloaded, compiled and installed the compiler (with
> prefix=/usr/local/gcc-2.3.3). I see there some executables (cpp, gcc, g++,
> g77, which I know I will need, but also things like gcj, gcjh, gcov etc,
> which I don't know what's their purpose), some include files and some
They all have man pages. Generally you should not care.
> libraries.
> I guess the first thing to do is to inform the linker about these
> libraries. As they are in a non-standard location, I have to tell
> somehow ldconfig where to look for them. I don't expect it to look with a
> flashlight in all the dark corners of my system, for new libraries.
I am not sure this is "the first thing" - you only have to do that
at run-time. set LD_LIBRARY_PATH to /usr/local/gcc-2.3.3/lib (BTW,
this was meant to be 3.2.2, I guess). Read ld.so(8) for more info.
> Next, I have to tell the make process to use these tools. Are there any
> option arguments that can be given to make to this purpose, or I have to
> temporarily change the soft links of gcc & comp. ?
I think the easiest is to put /usr/local/gcc-2.3.3/bin first in the
path before compilations. Usually you can get away with only setting
CC to /usr/local/gcc-2.3.3/bin/gcc.
> In the end, will octave know to link to the proper run-time libraries ?
> Here I am completely in the dark.
As I said, LD_LIBRARY_PATH. Write a trivial script to do that and
run octave.
> Any answer or pointer to answers will be most welcome.
> Thanks a lot, Avraham
>
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
Didi
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
