* Problems with GSL for shared libraries
@ 2004-05-21 9:10 Elspeth Nickle and Ron Teather
2004-05-24 10:53 ` Brian Gough
0 siblings, 1 reply; 2+ messages in thread
From: Elspeth Nickle and Ron Teather @ 2004-05-21 9:10 UTC (permalink / raw)
To: gsl-discuss
[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]
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
[-- Attachment #2: Type: text/enriched, Size: 2331 bytes --]
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:
<bold>Elspeth-Nickles-Computer:/gsl-1.4 ejn$ </bold>./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.<bold>
</bold>Then, when I tried to download autoconf 25, I got the message
reproduced below. So I installed autoconf2.5 instead.<bold>
“Elspeth-Nickles-Computer:~ ejn$</bold> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Problems with GSL for shared libraries
2004-05-21 9:10 Problems with GSL for shared libraries Elspeth Nickle and Ron Teather
@ 2004-05-24 10:53 ` Brian Gough
0 siblings, 0 replies; 2+ messages in thread
From: Brian Gough @ 2004-05-24 10:53 UTC (permalink / raw)
To: Elspeth Nickle and Ron Teather; +Cc: gsl-discuss
Elspeth Nickle and Ron Teather writes:
> 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
The 'configure.in' file should be part of the GSL source.
--
Brian Gough
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-05-24 10:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-05-21 9:10 Problems with GSL for shared libraries Elspeth Nickle and Ron Teather
2004-05-24 10:53 ` Brian Gough
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).