Problems with GSL for shared libraries

Elspeth Nickle and Ron Teather elsp_ron@dsl.pipex.com
Fri May 21 09:10:00 GMT 2004


I want to use the GSL with shared libraries.  I am running MacOS 10.3. 
So I followed the instructions in the INSTALL file for GSL but now I 
have this error message:

Elspeth-Nickles-Computer:/gsl-1.4 ejn$ ./autogen.sh
aclocal: couldn't open `configure.in': No such file or directory
automake: couldn't open `configure.in': No such file or directory

-Here are the instructions I followed.

To build shared libraries you can install MacOS X versions of libtool,
automake and autoconf, and then reconfigure:

   1. Get the fink packaging tool (http://fink.sourceforge.net)
   2, Install fink's libtool14, automake, autoconf25.
   3. Regenerate GSL's configuration using ./autogen.sh in the
      top-level directory.
   4. ./configure, make


  -Here’s what happened when I followed the instructions.  I got the 
fink packaging tool no problem.

Then, when I tried to download autoconf 25, I got the message 
reproduced below.  So I installed autoconf2.5 instead.

“Elspeth-Nickles-Computer:~ ejn$  sudo apt-get install autoconf25
Password:
Reading Package Lists... Done
Building Dependency Tree... Done
Package autoconf25 has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the contents
of sources.list
However the following packages replace it:
   autoconf2.5 autoconf
E: Package autoconf25 has no installation candidate”

When I tried to download automake, I got the message reproduced below.  
So I installed automake1.4.

“Package automake has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and
never uploaded, has been obsoleted or is not available with the contents
of sources.list
However the following packages replace it:
   automake1.7 automake1.6 automake1.4
E: Package automake has no installation candidate”

It was after this that I returned to the gsl-1.4 directory and ran the 
./autogen.sh command which produced the error message.  Is there anyone 
who can tell me how to get around this?  I would be very grateful for 
any help.

Elspeth Nickle



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 2234 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gsl-discuss/attachments/20040521/73e45009/attachment.bin>


More information about the Gsl-discuss mailing list