RE: EXT :Re: octave_idx_type and fortran

[Miller, Herbert D (IS)]

I am so sorry, but I am not sure what you mean by " Please quote and reply 
inline on this mailing list as I asked before ".

I have created a script that modifies LD_LIBRARY_PATH to point to my tool chain 
libraries before the script runs octave.  This seems to be working.  Octave 
came up and allowed me to create a configuration file and then proceeded to the 
Octave GUI.

Now, the "make check" command is complaining with:  
   . . ./octave-4.0.0/libinterp/dldfcn/PKG_ADD:  . . . 
/octave-4.0.0/libinterp/dldfcn/__init_fltk__.oct:  failed to load:  
/usr/local/lib/libfltk_gl.so.1.3:  undefined symbol: 
_ZN18Fl_Xfont_On_Demand5valueev

This symbol IS defined in /usr/local/lib/libfltk.a

Is there a way to fix that one?  I made sure that /usr/local/lib was in 
LD_LIBRARY_PATH, but the same error remained.

>> -----Original Message-----
>> From: Mike Miller [mailto:address@hidden 
>> Sent: Monday, July 25, 2016 1:11 PM
>> To: Miller, Herbert D (IS)
>> Cc: address@hidden
>> Subject: EXT :Re: octave_idx_type and fortran
>>
>> Please quote and reply inline on this mailing list as I asked before.
>>
>> On Mon, Jul 25, 2016 at 17:42:03 +0000, Miller, Herbert D (IS) wrote:
>> What you mentioned is possible?  I built with a 4.9.3 that was part of 
>> a GNAT installation.  Do I need to add something to LD_LIBRARY_PATH, 
>> or do I need to make a soft link?

> There are several ways to do so, including overwriting system symbolic links 
> (probably a good way to break other things on your system), configuring 
> ld.so.conf (may be safe, may break other things), or setting  LD_LIBRARY_PATH.
>
> I am surprised that your installation did not address any of these crucial 
> changes.

>> How do I tell if either of these are GLIBCXX_3.4.15 or GLIBCXX_3.4.20, 
>> and how can I be sure that Octave can finds them? ... and how can I 
>> Octave library need both of them?

> This is basic dynamic library versioning, there are many resources on the web 
> to help answer questions like these, nothing specific to Octave here.
>
> For libstdc++, the last number of the version string corresponds to the last 
> number of the so version. So GLIBCXX_3.4.20 is the version string 
> corresponding to changes in libstdc++.so.6.0.20. If you have a program that 
> requires > a GLIBCXX_3.4.20 versioned symbol, then you must load
l> ibstdc++.so.6.0.20 or later to be able to run it.
>
> --
> mike

herb