Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 254393 - app-misc/pax-utils-0.1.19: compilation failure during portage update (emerge portage)
Summary: app-misc/pax-utils-0.1.19: compilation failure during portage update (emerge ...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-10 10:49 UTC by Vladimir
Modified: 2009-01-11 17:18 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
"emerge --info" output (emerge.info,3.13 KB, text/plain)
2009-01-10 10:57 UTC, Vladimir
Details
Complete build log file (build.log,1.80 KB, text/plain)
2009-01-10 11:00 UTC, Vladimir
Details
Environment file. (environment,93.74 KB, text/plain)
2009-01-10 11:03 UTC, Vladimir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir 2009-01-10 10:49:44 UTC
While installing gentoo linux by steps in the handbook I was proposed to update portage system. I ran "emerge portage" as it was proposed but received error message: ERROR: app-misc/pax-utils-0.1.19 failed. Earlier in the emerge out there were strings like that: x86_64-pc-linux-gnu-gcc -mtune=core2 -march=core2 -O2 -pipe -D_GNU_SOURCE -DVERSION="0.1.19" -o paxelf.o -c paxelf.c
Architecture: Intel Core2 Duo T5750 2GHz CPU, which was specified in CFLAGS.

Reproducible: Always

Steps to Reproduce:
1.During installation gentoo linux on amd64 architecture specify in make.conf: CFLAGS="-mtune=core2 -march=core2 -O2 -pipe"
2.Do other steps from handbook for installing Gentoo on amd64 platform till portage tree update - here, after emerge --sync, you should be advised to update portage system with "emerge portage" command.
3.Run "emerge portage".
Actual Results:  
After running "emerge portage" I've got error message: ERROR: app-misc/pax-utils-0.1.19 failed.
This stopped emerge from portage upgrade.

Expected Results:  
Upgrade of portage system.

Notebook IBM Lenovo R61i type 7650-E8G with Intel Core2 Duo T5750 2GHz CPU1
Comment 1 Vladimir 2009-01-10 10:57:50 UTC
Created attachment 177950 [details]
"emerge --info" output
Comment 2 Vladimir 2009-01-10 11:00:52 UTC
Created attachment 177951 [details]
Complete build log file

Build log file formed during package app-misc/pax-utils-0.1.19 build
Comment 3 Vladimir 2009-01-10 11:03:06 UTC
Created attachment 177953 [details]
Environment file.

Evironment file created by "emerge portage" during package app-misc/pax-utils-0.1.19 build.
Comment 4 Vladimir 2009-01-10 13:10:06 UTC
It seems that core2-switch for CFLAGS parameter of make.conf which is described on gcc home page is not included in macho.h header file of pax-utils package.
Comment 5 Davide Pesavento (RETIRED) gentoo-dev 2009-01-10 13:41:29 UTC
AFAIK, -march=core2/-mtune=core2 is supported since GCC 4.3.x, but you are using 4.1.2
Comment 6 Vladimir 2009-01-11 13:55:09 UTC
(In reply to comment #5)
> AFAIK, -march=core2/-mtune=core2 is supported since GCC 4.3.x, but you are
> using 4.1.2

I tried also flags "native" and "x86_64" - the same result. Only "nocona" was accepted by the compiler.
Is there a way to upgrade gcc during installation process? I tried to run "emerge -u gcc", but received "all packages are up-to-date".
Comment 7 Davide Pesavento (RETIRED) gentoo-dev 2009-01-11 15:07:28 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > AFAIK, -march=core2/-mtune=core2 is supported since GCC 4.3.x, but you are
> > using 4.1.2
> 
> I tried also flags "native" and "x86_64" - the same result. Only "nocona" was
> accepted by the compiler.

-march=native works only with >= GCC 4.2.0, you have to use nocona for 4.1.x

> Is there a way to upgrade gcc during installation process? I tried to run
> "emerge -u gcc", but received "all packages are up-to-date".
> 

You are running stable and the latest stable gcc version is 4.1.2, which you are already using.

This bug is INVALID.
Comment 8 Vladimir 2009-01-11 17:18:00 UTC
Agree. My fault. Thanks for comments.