Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Suddenly getting emerge errors.[SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 777
Location: Tokyo, Japan

PostPosted: Thu Oct 03, 2013 3:13 am    Post subject: Suddenly getting emerge errors.[SOLVED] Reply with quote

I tried to do a world update and got the following error. It is odd because up until yesterday I never received this error.

Quote:

WARNING: One or more updates have been skipped due to a dependency conflict:

x11-base/xorg-server:0

(x11-base/xorg-server-1.14.3::gentoo, ebuild scheduled for merge) conflicts with
<x11-base/xorg-server-1.13.99[-minimal] required by (x11-drivers/xf86-video-virtualbox-4.1.26::gentoo, installed)


So I uninstalled all of my virtualbox stuff including the referenced driver and tried again and got"
Quote:
>>> Verifying ebuild manifests
>>> Running pre-merge checks for x11-base/xorg-server-1.14.3
* gcc-config: Active gcc profile is invalid!
gcc-config: error: could not run/locate 'x86_64-pc-linux-gnu-cpp'
* ERROR: x11-base/xorg-server-1.14.3::gentoo failed (pretend phase):
* Sorry, but gcc earlier than 4.0 will not work for xorg-server.
*
* Call stack:
* ebuild.sh, line 93: Called pkg_pretend
* xorg-server-1.14.3.ebuild, line 124: Called die
* The specific snippet of code:
* [[ "${MERGE_TYPE}" != "binary" && $(gcc-major-version) -lt 4 ]] && \
* die "Sorry, but gcc earlier than 4.0 will not work for xorg-server."
*
* If you need support, post the output of `emerge --info '=x11-base/xorg-server-1.14.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-1.14.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/die.env'.
* Working directory: '/usr/lib64/portage/pym'
* S: '/var/tmp/portage/x11-base/xorg-server-1.14.3/work/xorg-server-1.14.3'

* Messages for package x11-base/xorg-server-1.14.3:

* ERROR: x11-base/xorg-server-1.14.3::gentoo failed (pretend phase):
* Sorry, but gcc earlier than 4.0 will not work for xorg-server.
*
* Call stack:
* ebuild.sh, line 93: Called pkg_pretend
* xorg-server-1.14.3.ebuild, line 124: Called die
* The specific snippet of code:
* [[ "${MERGE_TYPE}" != "binary" && $(gcc-major-version) -lt 4 ]] && \
* die "Sorry, but gcc earlier than 4.0 will not work for xorg-server."
*
* If you need support, post the output of `emerge --info '=x11-base/xorg-server-1.14.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-1.14.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/die.env'.
* Working directory: '/usr/lib64/portage/pym'
* S: '/var/tmp/portage/x11-base/xorg-server-1.14.3/work/xorg-server-1.14.3'


So I did a emerge --depclean and revdep-rebuildand tried again.

Quote:
>>> Verifying ebuild manifests
>>> Running pre-merge checks for x11-base/xorg-server-1.14.3
* gcc-config: Active gcc profile is invalid!
gcc-config: error: could not run/locate 'x86_64-pc-linux-gnu-cpp'
* ERROR: x11-base/xorg-server-1.14.3::gentoo failed (pretend phase):
* Sorry, but gcc earlier than 4.0 will not work for xorg-server.
*
* Call stack:
* ebuild.sh, line 93: Called pkg_pretend
* xorg-server-1.14.3.ebuild, line 124: Called die
* The specific snippet of code:
* [[ "${MERGE_TYPE}" != "binary" && $(gcc-major-version) -lt 4 ]] && \
* die "Sorry, but gcc earlier than 4.0 will not work for xorg-server."
*
* If you need support, post the output of `emerge --info '=x11-base/xorg-server-1.14.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-1.14.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/die.env'.
* Working directory: '/usr/lib64/portage/pym'
* S: '/var/tmp/portage/x11-base/xorg-server-1.14.3/work/xorg-server-1.14.3'

* Messages for package x11-base/xorg-server-1.14.3:

* ERROR: x11-base/xorg-server-1.14.3::gentoo failed (pretend phase):
* Sorry, but gcc earlier than 4.0 will not work for xorg-server.
*
* Call stack:
* ebuild.sh, line 93: Called pkg_pretend
* xorg-server-1.14.3.ebuild, line 124: Called die
* The specific snippet of code:
* [[ "${MERGE_TYPE}" != "binary" && $(gcc-major-version) -lt 4 ]] && \
* die "Sorry, but gcc earlier than 4.0 will not work for xorg-server."
*
* If you need support, post the output of `emerge --info '=x11-base/xorg-server-1.14.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-1.14.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-base/xorg-server-1.14.3/temp/die.env'.
* Working directory: '/usr/lib64/portage/pym'
* S: '/var/tmp/portage/x11-base/xorg-server-1.14.3/work/xorg-server-1.14.3'


I am not sure what changed between yesterday and today. The only thing I did was eix-sync. my gcc is also the most recent so don't understand the 4.0 message. Any ideas?


Last edited by Budoka on Thu Oct 03, 2013 6:15 am; edited 1 time in total
Back to top
View user's profile Send private message
eyoung100
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1428

PostPosted: Thu Oct 03, 2013 3:36 am    Post subject: Reply with quote

Code:
gcc-config -l<--Small L
gcc-config set <profile-name>
emerge -1v libtool
emerge xorg-x11

_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper
Back to top
View user's profile Send private message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 777
Location: Tokyo, Japan

PostPosted: Thu Oct 03, 2013 3:53 am    Post subject: Reply with quote

eyoung100 wrote:
Code:
gcc-config -l<--Small L
gcc-config set <profile-name>
emerge -1v libtool
emerge xorg-x11


Quote:
# gcc-config -l
* gcc-config: Active gcc profile is invalid!

[1] x86_64-pc-linux-gnu-4.7.3


Which is odd because I am running kernel 3.10.7 This is my only choice and it is stating invalid so how do i update my profile? Also what could have happened to have cause this problem?
Back to top
View user's profile Send private message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 777
Location: Tokyo, Japan

PostPosted: Thu Oct 03, 2013 4:47 am    Post subject: Reply with quote

I tried to re-emerge gcc to see if that fixed it. No dice.

Quote:
>>> Failed to emerge sys-devel/gcc-4.7.3-r1, Log file:

>>> '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/temp/build.log'

* Messages for package sys-devel/gcc-4.7.3-r1:

* ERROR: sys-devel/gcc-4.7.3-r1::gentoo failed (compile phase):
* failed to run configure
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 4319: Called toolchain_src_compile
* environment, line 5009: Called gcc_do_configure
* environment, line 2476: Called die
* The specific snippet of code:
* "${S}"/configure "${confgcc[@]}" || die "failed to run configure";
*
* If you need support, post the output of `emerge --info '=sys-devel/gcc-4.7.3-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.7.3-r1::gentoo'`.
*
* Please include /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build/gcc-build-logs.tar.bz2 in your bug report
*
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/build'
* S: '/var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3'


Quote:
emerge --info '=sys-devel/gcc-4.7.3-r1::gentoo' |wgetpaste
!!! No gcc found. You probably need to 'source /etc/profile'
!!! to update the environment of this terminal and possibly
!!! other terminals also.
Your paste can be seen here: http://bpaste.net/show/137414/


Last edited by Budoka on Thu Oct 03, 2013 5:28 am; edited 1 time in total
Back to top
View user's profile Send private message
kurly
Apprentice
Apprentice


Joined: 02 Apr 2012
Posts: 260

PostPosted: Thu Oct 03, 2013 4:57 am    Post subject: Reply with quote

Budoka wrote:
eyoung100 wrote:
Code:
gcc-config -l<--Small L
gcc-config set <profile-name>
emerge -1v libtool
emerge xorg-x11


Quote:
# gcc-config -l
* gcc-config: Active gcc profile is invalid!

[1] x86_64-pc-linux-gnu-4.7.3


Which is odd because I am running kernel 3.10.7 This is my only choice and it is stating invalid so how do i update my profile? Also what could have happened to have cause this problem?

This means your current profile is invalid, or otherwise not equal to the only current choice. Continue to follow the instructions by doing 'gcc-config set 1' (that's the number 1) and try again...

Also your kernel has very little to do with your compiler, at least in this context.
Back to top
View user's profile Send private message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 777
Location: Tokyo, Japan

PostPosted: Thu Oct 03, 2013 5:31 am    Post subject: Reply with quote

kurly wrote:
Budoka wrote:
eyoung100 wrote:
Code:
gcc-config -l<--Small L
gcc-config set <profile-name>
emerge -1v libtool
emerge xorg-x11


OK. But then this happens.
Quote:
# gcc-config -l
* gcc-config: Active gcc profile is invalid!

[1] x86_64-pc-linux-gnu-4.7.3


Which is odd because I am running kernel 3.10.7 This is my only choice and it is stating invalid so how do i update my profile? Also what could have happened to have cause this problem?

This means your current profile is invalid, or otherwise not equal to the only current choice. Continue to follow the instructions by doing 'gcc-config set 1' (that's the number 1) and try again...

Also your kernel has very little to do with your compiler, at least in this context.


Quote:
# gcc-config -l
* gcc-config: Active gcc profile is invalid!

[1] x86_64-pc-linux-gnu-4.7.3
# gcc-config set 1
* gcc-config: Could not locate 'set' in '/etc/env.d/gcc/' !


This is driving me nuts because to the best of my knowledge no changes were made to my system since yesterday. How could this have broken?
Back to top
View user's profile Send private message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 777
Location: Tokyo, Japan

PostPosted: Thu Oct 03, 2013 5:45 am    Post subject: Reply with quote

OK. I think I got it sorted out. Part of it was my confusion reading gcc-config -l output. I thought it was saying that the profile, of which there was only 1, was invalid. Looks like maybe no profile was selected at all.

The other bit of confusion is that the syntax should be "gcc-config 1" not gcc-config set 1. I discovered that accidentally on this thread.

https://forums.gentoo.org/viewtopic-t-839709-highlight-.html

Still don't know how or why it broke but think it is ok now.
Back to top
View user's profile Send private message
kurly
Apprentice
Apprentice


Joined: 02 Apr 2012
Posts: 260

PostPosted: Thu Oct 03, 2013 6:10 am    Post subject: Reply with quote

Budoka wrote:
OK. I think I got it sorted out. Part of it was my confusion reading gcc-config -l output. I thought it was saying that the profile, of which there was only 1, was invalid. Looks like maybe no profile was selected at all.

The other bit of confusion is that the syntax should be "gcc-config 1" not gcc-config set 1. I discovered that accidentally on this thread.

https://forums.gentoo.org/viewtopic-t-839709-highlight-.html

Still don't know how or why it broke but think it is ok now.
I am sorry for misleading you with the incorrect gcc-config command, you are correct to have done "gcc-config 1" without the word "set". I hope that the rest of my explanation was helpful. You are correct that no profile (no valid profile, anyway!) was selected, and I think that was the source of your problem -- which is now fixed.

Glad you were able to get everything working despite the slight mistake.
Back to top
View user's profile Send private message
Budoka
l33t
l33t


Joined: 03 Jun 2012
Posts: 777
Location: Tokyo, Japan

PostPosted: Thu Oct 03, 2013 6:15 am    Post subject: Reply with quote

kurly wrote:
Budoka wrote:
OK. I think I got it sorted out. Part of it was my confusion reading gcc-config -l output. I thought it was saying that the profile, of which there was only 1, was invalid. Looks like maybe no profile was selected at all.

The other bit of confusion is that the syntax should be "gcc-config 1" not gcc-config set 1. I discovered that accidentally on this thread.

https://forums.gentoo.org/viewtopic-t-839709-highlight-.html

Still don't know how or why it broke but think it is ok now.
I am sorry for misleading you with the incorrect gcc-config command, you are correct to have done "gcc-config 1" without the word "set". I hope that the rest of my explanation was helpful. You are correct that no profile (no valid profile, anyway!) was selected, and I think that was the source of your problem -- which is now fixed.

Glad you were able to get everything working despite the slight mistake.

Yes your explanation was helpful. I'd like to thank you and everyone else.

I have been lucky in that, to date, I have never had a problem that I wasn't able to eventually solve with the help of the forum members.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum