-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
./configure syntax error on line 4556 in CentOS 7.9 #115
Comments
I face the same issue. I believe Centos 7.9 has too old a version of pkg-config (0.27.1) supposedly the functionality relied upon here was added in 0.28.0 ? Please correct me if this is wrong....
Just for fun I snipped out the whole bash completion block from configure and was able to proceed. It broke at the make stage though. I believe GCC is too old on this platform, causing the error: Centos 7 is EOL this year, however quite a few people will be stuck on this release for one reason or another so it would be a nice thing to support. I'm happy to volunteer my services as a tester on this platform (IBM HH LTO5 external SAS and a HH IBM LTO4 in a Dell Powervault autoloader) |
You are not wrong :( For a newer g++ on CentOS 7 you can check Devloper Toolset 8 |
Can confirm that works, however OP will also need to install newer pkg-config e.g from rpm.pbone.net (usual disclaimer about replacing rpms from different releases)
I hope the above proves useful to you @caiolopesdasilva |
Hi Everyone, I have been trying to test YATM in an IBM LTO-8 tape system, which depends on stenc, to work.
Upon trying to run the commands in the README I am facing the following issue and I am not sure how to proceed, anyone have any clue or tips on how to solve this issue?
autoreconf --install or ./autogen.sh don't output any issues.
I believe most packages necessary are on the most recent versions, this is also based on stenc-2.0.0
automake.noarch 1.13.4-3.el7
autoconf.noarch 2.69-11.el7
m4.x86_64 1.4.16-10.el7
bash-completion.noarch 1:2.1-8.el7
My Linux knowledge is somewhat limited so any help would be appreciated here.
The text was updated successfully, but these errors were encountered: