GCC broken?
Michael Powell
nightrecon at hotmail.com
Tue Feb 2 21:40:10 UTC 2010
Bernt Hansson wrote:
> Hello listreaders!
>
> I'm trying to build qt4-webkit 4.6.1
> But it fails or i fail to build it. Is it GCC?
> The machine is not overheating an has a low load, it's my desktop.
>
I just did this upgrade a few days to maybe a week ago with no problems.
>
> Stop in /usr/home/user/disk2/ports/www/qt4-webkit.
Maybe it doesn't like your non-standard ports location? Maybe try
/usr/ports?
> ** Command failed [exit code 1]: /usr/bin/script -qa
> /tmp/portupgrade20100202-28371-iomdra-0 env UPGRADE_TOOL=portupgrade
> UPGRADE_PORT=qt4-webkit-4.5.2 UPGRADE_PORT_VER=4.5.2 make
> ** Fix the problem and try again.
> ---> Build of www/qt4-webkit ended at: Tue, 02 Feb 2010 09:51:56 +0100
> (consumed 00:11:53)
> ---> Upgrade of www/qt4-webkit ended at: Tue, 02 Feb 2010 09:51:56
> +0100 (consumed 00:11:54)
> ---> ** Upgrade tasks 5: 0 done, 0 ignored, 0 skipped and 3 failed
> ---> Skipping 'devel/qt4-linguist' (qt4-linguist-4.5.3) because a
> requisite package 'qt4-webkit-4.5.2' (www/qt4-webkit) failed (specify -k
> to force)
Since mine upgraded without problem I suspect there is nothing wrong with
GCC, unless somehow it got broken on your machine. Make buildworld and make
installworld will rebuild it. At any rate, I just ran a build on the
www/qt4-webkit-4.6.1 port here as a test and it is building fine for me.
Another possibility is hardware, with the front runner being memory. If the
process stops at random locations each time it is most likely hardware
related. A hardware problem causing such a thing would also most likely show
itself during a make buildworld as well. If it stops at the same place with
the same error every time it is probably software related. And I suspect
your non-standard ports tree location.
-Mike
More information about the freebsd-questions
mailing list