Unsolved Qt 4.8.6 gmake failed with segmentation fault under Vagrant/VirtualBox
-
[0_1511684678268_qt_segmentation_fault.txt](Uploading 100%)
I am building Qt 4.8.6 on Scientific Linux using gmake and after taking more than an hour it failed with this error. I am running it inside of Vagrant/VirtualBox. Is that because of limited RAM vagrant has? I have given it only 1024MB.
Are there precompiled Qt 4.8.6 binaries for RedHat variant Scientific Linux?
-
Hi And welcome.
Sadly the upload is still broken so not possible to see the actual error.1 GB ram seems not so much for OS + compiler but i cant say its that for sure.
There seems to be no precompiled
https://download.qt.io/official_releases/qt/4.8/4.8.6/Can I ask why you want/need such old version ?
-
I tried to upload the file again but it failed. https://gist.github.com/umrashrf/ee41119cda859cf28413d69ae249305d
I also tried again with:
./configure -opensource -no-webkit -no-qt3support -fast
And it was fast this time but same error.
https://gist.github.com/umrashrf/bb16bb4b831aa993f1a490ecca026b7cI am debugging issues in a software which was made a long time ago and it depends on Qt4. I did try Qt5 and couldn't compile on Scientific Linux 6.5 which is more like CentOS 6. I have a history of failing to install newer versions of software on CentOS 6.
-
@umair
Hi- kernel/qauthenticator.cpp:1436: internal compiler error: Segmentation fault
What version of gcc ? Would it be possible to try a newer one ?
I doubt its related to running out of memory but more likely compiler bug/
something else.https://bugreports.qt.io/browse/QTBUG-45974
Ok, good old maintenance :)
- failing to install newer versions of software on CentOS 6.
But if you are using virtual machines, cant you just use another linux variant if
CentOS 6 is troublesome ? -
[vagrant@localhost qt-everywhere-opensource-src-4.8.6]$ gcc --version
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-18)
Copyright (C) 2010 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. -
Ok that is pretty old :)
Im trying to find out what gcc version is expected for 4.8.6 since
it might be that. -
But if you are using virtual machines, cant you just use another linux variant if
CentOS 6 is troublesome ?Can't. It's a school project :)
The idea is to grab a version of Scientific Linux 6 from the official website and run a bunch of scripts to meet deps and then install the aged software.
I am going to do the same for Scientific Linux 7 and will use the newer versions of deps.
If the conclusion is to not use Scientific Linux 6 then it's not a solution. I have the liberty to convince people to move to newer OS and that'd be very easy for me but it's like giving up very early :)
-
@umair
Oh. i did not mean to give up Scientific Linux 6.
Just asking as sometimes developers can use one version of Os to develop for other
version. Like its possible to use win 10 to make app for win xp. Where as
running the compiler on win Xp is not supported.
Same applies to linux. you could produce programs from linux distro X to
say CentOS 6.But i think you will need a newer gcc.
Is that possible ? -
I can upgrade gcc but I am afraid it will break other stuff. Let me try it anyway with version gcc 4.9.
Could you find which gcc version it should work with?
-
@umair
Use copy of virtual machine so if it breaks it wont matter :)Well i cant as it dont go that far back
https://doc.qt.io/qt-5/supported-platforms-and-configurations.htmlBut im sure some of the others will know.
I found some docs hinting gcc 4.4 but could not really find solid doc.
-
thanks @mrjj
-
@umair
Currently trying building 4.8.6 in mint linux just to see
it does in fact just build with newer gcc.
(its gcc 5.4 (2015) )Update:
did just build.So good chances a slightly newer gcc will work.
-
@mrjj my gcc make is still running :)
-
@umair
If you are using a multi core system make sure to use
make -jX
so it uses all cores it can get. that speeds up considerably
X being your numbers of coresps. crossing fingers :)