|
|
 Up |
|
|
  |
Date: Jun 15, 2008 03:37
Hi,
I'm trying to install the latest source-version of Scilab, but run into
this:
checking dynamic linker characteristics... solaris2.10 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... no
appending configuration tag "F77" to libtool
end of configuration of libtool
checking for f77... no
checking for f90... no
checking for f2c-f77... no
configure: error: Unable to configure: Fortran f77 compiler not found
$
# pkginfo | grep g77
application CSWgcc3g77rt gcc3g77rt - GNU FORTRAN 77
Compiler Run Time
$ echo $PATH
/usr/local/qt/bin:/usr/bin:/usr/openwin/bin:/usr/ucb:/usr/sfw/bin:/opt/csw/bin:/opt/csw/bin
|
| Show full article (0.84Kb) |
|
| | 8 Comments |
|
|
Author: Jean-Pierre VialJean-Pierre Vial Date: Jun 15, 2008 10:08
Huub a écrit :
> Hi,
>
> I'm trying to install the latest source-version of Scilab, but run into
> this:
>
> checking dynamic linker characteristics... solaris2.10 ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... no
> appending configuration tag "F77" to libtool
> end of configuration of libtool
> checking for f77... no
> checking for f90... no
> checking for f2c-f77... no
> configure: error: Unable to configure: Fortran f77 compiler not found
> $
>
> # pkginfo | grep g77
> application CSWgcc3g77rt gcc3g77rt - GNU FORTRAN 77
> Compiler Run Time ...
|
| Show full article (1.20Kb) |
|
| | no comments |
|
|
Date: Jun 17, 2008 01:19
> try to set the relevant environment variables:
> first type ./configure --help to see the list
> then either something like
> ./configure CC=xxxxxx F77=yyyyyy [options]
> or
> export CC=xxxxx
> export F77=yyyyyy
> ./configure [options]
>
> where xxxxx and yyyyy are the absolute paths to the executable
OK, this works. What about this:
checking for header file tcl.h... configure: error: no header file tcl.h
found for 8.4*
I adjusted the PATH for this, but that doesn't work. Any idea?
|
| |
| no comments |
|
|
Author: Jean-Pierre VialJean-Pierre Vial Date: Jun 17, 2008 01:35
Huub a écrit :
>> try to set the relevant environment variables:
>> first type ./configure --help to see the list
>> then either something like
>> ./configure CC=xxxxxx F77=yyyyyy [options]
>> or
>> export CC=xxxxx
>> export F77=yyyyyy
>> ./configure [options]
>>
>> where xxxxx and yyyyy are the absolute paths to the executable
>
> OK, this works. What about this:
>
> checking for header file tcl.h... configure: error: no header file tcl.h
> found for 8.4*
>
> I adjusted the PATH for this, but that doesn't work. Any idea?
check that
1 you do have tcl.h ...
|
| Show full article (0.92Kb) |
| no comments |
|
|
Date: Jun 17, 2008 02:13
Jean-Pierre Vial wrote:
> Huub a écrit :
>>> try to set the relevant environment variables:
>>> first type ./configure --help to see the list
>>> then either something like
>>> ./configure CC=xxxxxx F77=yyyyyy [options]
>>> or
>>> export CC=xxxxx
>>> export F77=yyyyyy
>>> ./configure [options]
>>>
>>> where xxxxx and yyyyy are the absolute paths to the executable
>> OK, this works. What about this:
>>
Ok, checked and adjusted the ./configure. Now it ends with this:
|
| Show full article (2.51Kb) |
| no comments |
|
|
Author: Jean-Pierre VialJean-Pierre Vial Date: Jun 17, 2008 05:21
Huub a écrit :
> Jean-Pierre Vial wrote:
>> Huub a écrit :
>>>> try to set the relevant environment variables:
>>>> first type ./configure --help to see the list
>>>> then either something like
>>>> ./configure CC=xxxxxx F77=yyyyyy [options]
>>>> or
>>>> export CC=xxxxx
>>>> export F77=yyyyyy
>>>> ./configure [options]
>>>>
>>>> where xxxxx and yyyyy are the absolute paths to the executable
>>> OK, this works. What about this:
>>>
>
> Ok, checked and adjusted the ./configure. Now it ends with this:
>
> ----------
> checking for header file tcl.h... found in /opt/csw/include ...
|
| Show full article (3.00Kb) |
| no comments |
|
|
Date: Jun 17, 2008 05:30
> look for something like libtcl8.4.so
> and try to adjust the configure options so that the directory is found
> if I remember well, there are two options for tcl and two for tk,
> one of them should point to the zzzzz.so files
> You may also have a very old version of tcl and tk, but this would be
> surprising.
> I can suggest no other idea --with-tcl-include=/opt/csw/include --with-tcl-library=/opt/csw/lib
I use the tcl from Blastwave, installed using pkg-get.
|
| |
| no comments |
|
|
Author: Jean-Pierre VialJean-Pierre Vial Date: Jun 17, 2008 08:07
Huub a écrit :
>> look for something like libtcl8.4.so
>> and try to adjust the configure options so that the directory is found
>> if I remember well, there are two options for tcl and two for tk,
>> one of them should point to the zzzzz.so files
>> You may also have a very old version of tcl and tk, but this would be
>> surprising.
>> I can suggest no other idea >
> $ find /opt/ -name libtcl8.4.so
> / opt/csw/lib/libtcl8.4.so
>
>
> Still getting the same result, using this configure:
>
> ./configure F77=/opt/csw/gcc3/bin/g77
> --with-tcl-include=/opt/csw/include --with-tcl-library=/opt/csw/lib
>
> I use the tcl from Blastwave, installed using pkg-get.
|
| Show full article (1.67Kb) |
| no comments |
|
|
|
|
|
Date: Jun 17, 2008 08:53
> --with-tk-include=/opt/csw/include --with-tk-library=/opt/csw/lib
> is needed also, but you probably added it already
>
> I have no further idea
That didn't work out as well. Thank you for helping.
>
> Maybe you could try --without-tk as a test
> if it works, it will compile a console-only scilab,
> which can be of (limited) use, but mainly it will make you sure that the
> problem is really with tcl and tk and not something else hidden
> by a wrong error message
>
> I had little success with recent versions of scilab on ultrasparc, my
> SUN machine still has a 4.0-beta version or something like that
Too bad they don't provide scilab (yet) through Blastwave. They do with
Octave.
|
| Show full article (1.38Kb) |
| no comments |
|
RELATED THREADS |
|
|
|
|
