I've downloaded
wget https://www-fourier.ujf-grenoble.fr/~pa ... 996.tar.gz
Extracted it and cd to new created folder.
When I do ./configure it gives this error
checking for sstream... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'
This ONLY happens under windows 10 WSL 2.0 linux, running
>uname -a
Linux DESKTOP-0HFNTFN 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Running default Ubuntu installed from microsoft store
>cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
I've never had this error before with giac. If I do the same thing (i.e. download and extract and run ./configure) on Linux running inside Virtual box (ie not using WSL 2.0) then it works OK. This error do not show up.
So it has to do with using WSL.
Could someone try to run ./configure on WSL and see if they get same error?
I've put a link to the config.log below
https://12000.org/tmp/giac_error/giac_config.log
I'd like to move to WSL since easier to use than Virtual box, but this issue is making it hard to build giac.
Thanks
--Nasser
Unable to run ./configure on WSL. config.status: error: cannot find input file: `Makefile.in'
Modérateur : xcasadmin
Re: Unable to run ./configure on WSL. config.status: error: cannot find input file: `Makefile.in'
I tried on WSL with debian, configure is running.
Perhaps, check sstream installation and try again?
Perhaps, check sstream installation and try again?
Code : Tout sélectionner
configure:23990: WARNING: sstream: present but cannot be compiled
configure:23990: WARNING: sstream: check for missing prerequisite headers?
configure:23990: WARNING: sstream: see the Autoconf documentation
configure:23990: WARNING: sstream: section "Present But Cannot Be Compiled"
configure:23990: WARNING: sstream: proceeding with the compiler's result
configure:23990: checking for sstream
configure:23990: result: no
Re: Unable to run ./configure on WSL. config.status: error: cannot find input file: `Makefile.in'
"Perhaps, check sstream installation and try again?"
Could you please be more explicit? What exactly do I need to do? What is sstream installation?
These are the compiler versions used
-------------------------------
>which c++
/usr/bin/c++
>c++ --version
c++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>gcc --version
gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>which gcc
/usr/bin/gcc
>
>which g++
/usr/bin/g++
>g++ --version
g++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
----------------------------------
I know ./configure says there is no sstream at end before the error:
---------------------
.......
checking for dvips... /usr/local/texlive/2024/bin/x86_64-linux/dvips
checking sstream usability... no
checking sstream presence... yes
configure: WARNING: sstream: present but cannot be compiled
configure: WARNING: sstream: check for missing prerequisite headers?
configure: WARNING: sstream: see the Autoconf documentation
configure: WARNING: sstream: section "Present But Cannot Be Compiled"
configure: WARNING: sstream: proceeding with the compiler's result
checking for sstream... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'
>
------------------------------------------
Do I need to install sstream? How? Never heard of it before this time.
Is the g++ compiler used not the correct version?
I just did
-------------------
>sudo apt update && sudo apt install build-essential
[sudo] password for me:
Get:1 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease
Get:3 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components [7264 B]
Get:4 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Components [52.0 kB]
Get:5 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Components [212 B]
Get:6 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 Components [212 B]
Get:7 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Get:8 http://archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
Get:9 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Components [151 kB]
Get:10 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Components [309 kB]
Get:11 http://archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Components [212 B]
Get:12 http://archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Components [940 B]
Get:13 http://archive.ubuntu.com/ubuntu noble-backports/main amd64 Components [208 B]
Get:14 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Components [11.7 kB]
Get:15 http://archive.ubuntu.com/ubuntu noble-backports/restricted amd64 Components [216 B]
Get:16 http://archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Components [212 B]
Fetched 912 kB in 1s (609 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
15 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
build-essential is already the newest version (12.10ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
>
---------------------------------------------------
And as you see, it says the compiler is up to date.
I also did
sudo apt update
sudo apt upgrade
And SSTREAM error message is still there.
Again, this only happens on windows WSL 2.0 with Ubuntu. Does not happen on any other
linux under virtual box.
--Nasser
Could you please be more explicit? What exactly do I need to do? What is sstream installation?
These are the compiler versions used
-------------------------------
>which c++
/usr/bin/c++
>c++ --version
c++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>gcc --version
gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>which gcc
/usr/bin/gcc
>
>which g++
/usr/bin/g++
>g++ --version
g++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
----------------------------------
I know ./configure says there is no sstream at end before the error:
---------------------
.......
checking for dvips... /usr/local/texlive/2024/bin/x86_64-linux/dvips
checking sstream usability... no
checking sstream presence... yes
configure: WARNING: sstream: present but cannot be compiled
configure: WARNING: sstream: check for missing prerequisite headers?
configure: WARNING: sstream: see the Autoconf documentation
configure: WARNING: sstream: section "Present But Cannot Be Compiled"
configure: WARNING: sstream: proceeding with the compiler's result
checking for sstream... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'
>
------------------------------------------
Do I need to install sstream? How? Never heard of it before this time.
Is the g++ compiler used not the correct version?
I just did
-------------------
>sudo apt update && sudo apt install build-essential
[sudo] password for me:
Get:1 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease
Get:3 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components [7264 B]
Get:4 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Components [52.0 kB]
Get:5 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Components [212 B]
Get:6 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 Components [212 B]
Get:7 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Get:8 http://archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
Get:9 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Components [151 kB]
Get:10 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Components [309 kB]
Get:11 http://archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Components [212 B]
Get:12 http://archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Components [940 B]
Get:13 http://archive.ubuntu.com/ubuntu noble-backports/main amd64 Components [208 B]
Get:14 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Components [11.7 kB]
Get:15 http://archive.ubuntu.com/ubuntu noble-backports/restricted amd64 Components [216 B]
Get:16 http://archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Components [212 B]
Fetched 912 kB in 1s (609 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
15 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
build-essential is already the newest version (12.10ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
>
---------------------------------------------------
And as you see, it says the compiler is up to date.
I also did
sudo apt update
sudo apt upgrade
And SSTREAM error message is still there.
Again, this only happens on windows WSL 2.0 with Ubuntu. Does not happen on any other
linux under virtual box.
--Nasser
Re: Unable to run ./configure on WSL. config.status: error: cannot find input file: `Makefile.in'
fyi,
I tried number of Linux distros on virtual box, and they all fail with same error when using ./configure.
I ended up installing Arch based distro (EOS) and installed giac from the package manager directly
me@me-virtualbox TMP]$ pacman -Q| grep giac
giac 1.9.0.998-1
And this worked.
There is some problem building giac from sources. configure does not like something.
But using pacman package manager (Arch) I am able now to get latest giac, so I am ok now.
--Nasser
I tried number of Linux distros on virtual box, and they all fail with same error when using ./configure.
I ended up installing Arch based distro (EOS) and installed giac from the package manager directly
me@me-virtualbox TMP]$ pacman -Q| grep giac
giac 1.9.0.998-1
And this worked.
There is some problem building giac from sources. configure does not like something.
But using pacman package manager (Arch) I am able now to get latest giac, so I am ok now.
--Nasser
Re: Unable to run ./configure on WSL. config.status: error: cannot find input file: `Makefile.in'
sstream is part of the standard c++ library. If it is not detected by configure, it's probably because the devel headers of libstdc++ are not installed
Re: Unable to run ./configure on WSL. config.status: error: cannot find input file: `Makefile.in'
That could be it. But I am on Arch linux based distro (EOS) and I do not know exactly which package to install to get these c++ headers.
But since arch based distros have latest giac, then from now on, I will just use pacman to install giac. Much easier and do not need to deal with configure and make sure all prerequisites are there.
The configure script should really tell the user what is missing instead of just giving an error that it can not find Makefile.in.
But since arch based distros have latest giac, then from now on, I will just use pacman to install giac. Much easier and do not need to deal with configure and make sure all prerequisites are there.
The configure script should really tell the user what is missing instead of just giving an error that it can not find Makefile.in.