Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
libid3tab fails due to depreciated -mtune=x86-64
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
FastTurtle
Guru
Guru


Joined: 03 Sep 2002
Posts: 431
Location: Flakey Shake & Bake Caliornia, USA

PostPosted: Wed Jul 03, 2019 2:40 pm    Post subject: libid3tab fails due to depreciated -mtune=x86-64 Reply with quote

libid3tag fails due to -mtune=x86-64 instead of generic. Problem is, according to the gentoo docs, generic is not supported by everything and tends to build for all CPU's from i386 and up, which I don't want as I prefer a generic x86-64 build.

Current work around is to simply remove the -mtune from make.conf but I'd rather know of a better solution instead of fragging the entire build and having to go individual flags for every package.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 15334

PostPosted: Thu Jul 04, 2019 12:40 am    Post subject: Reply with quote

Try using a full value -mtune=x86-64 instead of a depreciated one. If that doesn't work, please post the standard debug data that Portage suggests when a build fails. You probably don't need -mtune at all. For most users, setting an appropriate -march is sufficient.
Back to top
View user's profile Send private message
FastTurtle
Guru
Guru


Joined: 03 Sep 2002
Posts: 431
Location: Flakey Shake & Bake Caliornia, USA

PostPosted: Thu Jul 04, 2019 4:58 pm    Post subject: Reply with quote

Hu: libid3tag failed to build using the -mtune=x86-64, saying that was deprecated. Use Generic Instead.

Either we have a package mismatch (it's insisting on next gcc version feature) or a package got pulled in unexpectedly with the dependency on the latest gcc. Have to look at the package version to see.

Stipped the -mtune=x86-64 from make.conf and had no issue afterwards but it is frustrating when a package is insisting it needs the latest (Shinies!!!) to build correctly.

On a related front, seems that the package.db site is not working with Firefox 60.7 esr (kept getting 500 errors).

As this is part of my flashgentoo project, I need the mtune=x86-64 to work correctly as I have no idea if the flash drive will be booting an Intel or AMD based system and keep in mind that some of us are restricted from using the (Shinies!!) due to regulatory reasons. In other words, if it aint been blessed, it's not allowed.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 15334

PostPosted: Fri Jul 05, 2019 2:34 am    Post subject: Reply with quote

FastTurtle wrote:
Hu: libid3tag failed to build using the -mtune=x86-64, saying that was deprecated. Use Generic Instead.
I see nothing in the ebuild that would do this, so this is probably coming from the upstream package.
FastTurtle wrote:
Either we have a package mismatch (it's insisting on next gcc version feature) or a package got pulled in unexpectedly with the dependency on the latest gcc. Have to look at the package version to see.
I don't understand what you are trying to say here.
FastTurtle wrote:
Stipped the -mtune=x86-64 from make.conf and had no issue afterwards but it is frustrating when a package is insisting it needs the latest (Shinies!!!) to build correctly.
Gentoo is not forcing anything to be shiny. None of the output you have provided supports that any particular level of shine is required.
FastTurtle wrote:
On a related front, seems that the package.db site is not working with Firefox 60.7 esr (kept getting 500 errors).
Most people would stop after a dozen or so errors. However, there was a recent report that packages.gentoo.org was experiencing problems.
FastTurtle wrote:
As this is part of my flashgentoo project, I need the mtune=x86-64 to work correctly as I have no idea if the flash drive will be booting an Intel or AMD based system and keep in mind that some of us are restricted from using the (Shinies!!) due to regulatory reasons. In other words, if it aint been blessed, it's not allowed.
This makes no sense to me. -mtune has no impact on which systems can or cannot run the resulting code. Per the documentation, you are thinking of -march, which can produce code that requires the specified CPU. -mtune merely encourages the compiler to pick sequences that perform optimally for that CPU, but does not permit it to generate code which requires that CPU.

As I requested above, please post standard debug data for a specific problem which you want assistance solving.
Back to top
View user's profile Send private message
FastTurtle
Guru
Guru


Joined: 03 Sep 2002
Posts: 431
Location: Flakey Shake & Bake Caliornia, USA

PostPosted: Fri Jul 05, 2019 3:04 pm    Post subject: Reply with quote

I'm going to mark this one as closed as it appears to have been a glitch. Later tests haven't shown the same issue.

On the package mismatch - suspect it was something pulled in during the -epv --deep --Newuse @world stage of the amd64 handbook (suspect the deep flag caused the issue). Total number of packages pulled in was 198 for the world rebuild, yet the only change to the profile I made was to amd64-desktop.

Other test builds have not shown the same issue, so as stated, I'm going to close it since it appears as a one time glitch.
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