Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Trouble with sources [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
todd93
Guru
Guru


Joined: 30 Oct 2006
Posts: 524
Location: Missouri

PostPosted: Fri Oct 27, 2017 11:01 pm    Post subject: Trouble with sources [SOLVED] Reply with quote

Hi, all, I'm stuck on my sources, I have gotten all the disk work done, chrooted into my environment, but while emerging sys-devel/bc-1.06.95-r1 I get this log. I'm not sure what is causing this and am able to post any other information needed.

Thanks

Todd


Last edited by todd93 on Sat Oct 28, 2017 1:32 am; edited 1 time in total
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13987

PostPosted: Fri Oct 27, 2017 11:12 pm    Post subject: Reply with quote

You have three problems. The first is that you have hit a bug that the ebuild uses econf without an explicit die while using an EAPI that does not have an implicit die. This causes the ebuild to push on after the first failure, producing a second unhelpful failure later. Please report this to the Gentoo maintainer. Normally, a failure in econf should abort the whole ebuild immediately, but in this case it did not.

Your second problem is that you did not post the output of emerge --info nor a link to a recent copy of it. This is often helpful for us to help you.

Your third problem is that econf failed and told you to post the configure log, but you did not post it. We need that log to help you. If I were to guess blindly, I would say that you specified non-working CFLAGS, so econf reported the compiler as broken. In my experience, this is the single most common explanation for "C compiler cannot create executables".
https://paste.pound-python.org/show/OqyHuRg6hyJ6SVm2Xdhr/:
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95/config.log
econf failed
Back to top
View user's profile Send private message
todd93
Guru
Guru


Joined: 30 Oct 2006
Posts: 524
Location: Missouri

PostPosted: Fri Oct 27, 2017 11:40 pm    Post subject: Reply with quote

Hu wrote:
You have three problems. The first is that you have hit a bug that the ebuild uses econf without an explicit die while using an EAPI that does not have an implicit die. This causes the ebuild to push on after the first failure, producing a second unhelpful failure later. Please report this to the Gentoo maintainer. Normally, a failure in econf should abort the whole ebuild immediately, but in this case it did not.

Your second problem is that you did not post the output of emerge --info nor a link to a recent copy of it. This is often helpful for us to help you.

Your third problem is that econf failed and told you to post the configure log, but you did not post it. We need that log to help you. If I were to guess blindly, I would say that you specified non-working CFLAGS, so econf reported the compiler as broken. In my experience, this is the single most common explanation for "C compiler cannot create executables".
https://paste.pound-python.org/show/OqyHuRg6hyJ6SVm2Xdhr/:
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-devel/bc-1.06.95-r1/work/bc-1.06.95/config.log
econf failed


I'm sorry, Hu, I realize I forgot the other info. Please bear with me, here's my emerge --info. And here is the config.log for the package in question. Hopefully this clears up 2 of the 3 issues with my post. And thank you again!
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7133
Location: Saint Amant, Acadiana

PostPosted: Sat Oct 28, 2017 12:08 am    Post subject: Reply with quote

Code:
conftest.c:1:0: error: bad value (znver1) for -march= switch

Why not use -march=native ? Obviously gcc-5.4 does not recognize znver1 as valid.
_________________
Please learn how to denote units correctly!


Last edited by Jaglover on Sat Oct 28, 2017 12:09 am; edited 1 time in total
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7072

PostPosted: Sat Oct 28, 2017 12:08 am    Post subject: Reply with quote

So usual problem that Hu guess it :)
Code:
conftest.c:1:0: error: bad value (znver1) for -march= switch

with
CFLAGS="-O2 -march=znver1"

In doubt, always use -march=native, if you need more help on the subject, look in the forum you have a special thread for ryzen cpu owner.
Back to top
View user's profile Send private message
todd93
Guru
Guru


Joined: 30 Oct 2006
Posts: 524
Location: Missouri

PostPosted: Sat Oct 28, 2017 1:32 am    Post subject: Reply with quote

LOL I feel like such a fool, I was confused in the handbook when it came to the CFLAGS and gcc. I fixed the CFLAG entry, and all emerged well.

Thanks for the help!

Todd
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo 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