OS/2, eCS & ArcaOS - Technical > Programming
Strange autoconf / autoreconf / configure behavior
Dave Yeo:
And what shell are you using?
Mentore:
--- Quote from: Dave Yeo on June 19, 2024, 05:16:42 pm ---And what shell are you using?
--- End quote ---
KO, Dave, thanks.
Perl installed and I'm using sh as default shell.
The really really strange thing is that everything used to work until someday this happened.
And I really can't understand why :o
I wonder if this has something to do with a certain clean.exe software I installed in lieu of the already present one in /usr/bin, but I don't know what the correlation may be.
I'll try something this morning changing che autotools with the latest version provided by KO and report back.
The toolchain works, by the way - I was able to recreate an OS/2 version of ZesarUX (https://github.com/chernandezba/zesarux), a really interesting multi machines emulator under SDL. It seems OS/2 finally has his Sinclair QL emulator 8)
Thanks again!
Mentore
Mentore:
--- Quote from: Mentore on June 20, 2024, 07:53:25 am ---
--- Quote from: Dave Yeo on June 19, 2024, 05:16:42 pm ---And what shell are you using?
--- End quote ---
KO, Dave, thanks.
Perl installed and I'm using sh as default shell.
The really really strange thing is that everything used to work until someday this happened.
And I really can't understand why :o
I wonder if this has something to do with a certain clean.exe software I installed in lieu of the already present one in /usr/bin, but I don't know what the correlation may be.
I'll try something this morning changing che autotools with the latest version provided by KO and report back.
The toolchain works, by the way - I was able to recreate an OS/2 version of ZesarUX (https://github.com/chernandezba/zesarux), a really interesting multi machines emulator under SDL. It seems OS/2 finally has his Sinclair QL emulator 8)
Thanks again!
Mentore
--- End quote ---
Re-quoting myself.
I am still in the midst of this... I edited libtoolize, aclocal, autoconf, autoreconf and some other files to remove every instance of the string "/@unixroot" since it seemed to cause troubles.
Trying to run autoconf, autoreconf and aclocal from scripts and command line I always receive the same error in aclocal:
From ksh
Running aclocal
Can't open perl script "exe": No such file or directory
aclocal: error: echo failed with exit status: 2
Error: aclocal failed
Similar error occur if I try from sh or ash. I'm starting to get frustrated, since everything worked great before...
Maybe a complete system reinstallation would be needed. I'll think about that.
Mentore
KO Myung-Hun:
Which drive are you working on ?
And what does UNIXROOT env var set to ?
How did you install your auto-tools ?
Where is your `sh' from ?
Mentore:
--- Quote from: KO Myung-Hun on June 20, 2024, 02:48:42 pm ---Which drive are you working on ?
And what does UNIXROOT env var set to ?
How did you install your auto-tools ?
Where is your `sh' from ?
--- End quote ---
Hello mate,
UNIXROOT points to D: drive where I put usr/ directory and every relevant subdirectory.
auto-tools installed via ANPM and worked fine until this suddendly happened.
Also, sh, ash and ksh come with the standard development tools gotten via ANPM.
Can't get a clue of what's changed, but one day a configure script was perfect, the next day this error pops up from the very same script. Since then, no success in generating makefiles.
Mind you, CMake works, make works, so if I can arrange or modify an existing makefile I'm fine and everything works well (doesn't mean I get a really useful executable 100% of the times, but this is normal in porting software).
So I'm guessing a system reinstall may be useful...
Mentore
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version