Summary: | media-libs/xvid-1.3.3: fails to build on ppc, "C compiler cannot create executables" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ernsteiswuerfel <erhard_f> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bkohler |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
config.log |
Description
ernsteiswuerfel
![]() Created attachment 446020 [details]
build.log
See `config.log' for more details !!! Please attach the following file when seeking support: !!! /var/tmp/portage/media-libs/xvid-1.3.3/work/xvidcore/build/generic-abi_ppc_32.ppc/config.log Created attachment 446024 [details]
config.log
powerpc-unknown-linux-gnu-gcc: error: unrecognized command line option '-march=native' I dont think you can use -march=native on ppc True. You can't use -march=native on ppc as you pointed out. Only -mcpu and -mtune are available on ppc/ppc64 in gcc. This is the case from gcc 4.9.x to 6.x.x. I have been noticing that several packages are having problems with that, now that I am building my first ppc system up. ;-) I am running this profile: [11] default/linux/powerpc/ppc64/13.0/32bit-userland/desktop/gnome/systemd * And in my make.conf I got: CFLAGS="-mcpu=G5 -mtune=G5 -Os -pipe" CXXFLAGS="${CFLAGS}" The ebuild seems to ignore that. Is there anything special about your build environment? Are you using any kind of emerge wrapper script, or crossdev from another host, or distcc, or qemu+chroot? I don't see any way these CFLAGS could be coming from the packages' own build systems, they must be from the outside somehow. *** This bug has been marked as a duplicate of bug 594000 *** (In reply to Ben Kohler from comment #6) > Is there anything special about your build environment? Are you using any > kind of emerge wrapper script, or crossdev from another host, or distcc, or > qemu+chroot? > > I don't see any way these CFLAGS could be coming from the packages' own > build systems, they must be from the outside somehow. I am also clueless where these CFLAGS are coming from. All the building is done locally on the machine. It's reasonably fast to handle that (2,3 MHz dual CPU). See comment 8 on bug 594000. |