Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 87050 - avr-libc fails on x86_64 2005.0 because of added CFLAGS
Summary: avr-libc fails on x86_64 2005.0 because of added CFLAGS
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Embedded Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-28 17:47 UTC by Scott Price
Modified: 2005-07-28 13:22 UTC (History)
2 users (show)

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


Attachments
new ebuild that blocks CFLAGS_amd64 and CFLAGS_x86 (avr-libc-1.2.3-r1.ebuild,987 bytes, text/plain)
2005-03-28 17:57 UTC, Scott Price
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Price 2005-03-28 17:47:47 UTC
I had to mask off CFLAGS_amd64 and CFLAGS_x86 because they cause the compile to fail as the target is not the same as the host.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Scott Price 2005-03-28 17:57:49 UTC
Created attachment 54732 [details]
new ebuild that blocks CFLAGS_amd64 and CFLAGS_x86
Comment 2 Jan Brinkmann (RETIRED) gentoo-dev 2005-03-29 05:05:39 UTC
according to the metadata.xml, this has not much to do with media-video@g.o:

        <herd>dev-embedded</herd>

        <maintainer>
                <email>dragonheart@gentoo.org</email>
                <name>Daniel Black</name>
        </maintainer>

reassigning :)
Comment 3 SpanKY gentoo-dev 2005-03-29 05:57:53 UTC
this does bring up a good side point ... are the CFLAG abi variables going to screw everything up for cross-compiling ?
Comment 4 Scott Price 2005-03-29 09:05:52 UTC
I was wondering the same thing.

This one confused me greatly when I was trying to debug it.  GCC kept failing saying the argument '64' was invalid.  There was nothing on the command line that said anything about 64.  I finally had the ebuild print out its enviromental variables and there were these two CFLAGS.  When I cleared them everything worked.  It was kind of disturbing that they didn't show up on the command line print out.  They must be in the gcc wrapper somewhere.

Scott  =)
Comment 5 Scott Price 2005-04-06 19:55:45 UTC
I think that if strip-unsupported-flags and strip-flags from flag-o-matic.eclass stripped CFLAGS_amd64 and CFLAGS_x86 also the extra cflags wouldn't hurt cross compiling nearly as much.

Should I enter this as a separate bug?  I have a new ebuild that should work if those two functions were updated.  I can also check into updating them.

Scott  =)
Comment 6 SpanKY gentoo-dev 2005-04-06 19:57:21 UTC
no ... abi CFLAGS should not be breaking crap like this

i'll chat with eradicator about it
Comment 7 Scott Price 2005-04-15 14:15:29 UTC
Those two break every cross compile on my system.  It is not just the AVR stuff.   I am currently trying PPC.  This is what I get trying to compile cross-i686-pc-linux-gnu/linux-headers:


CRC-CCITT functions (CRC_CCITT) [N/m/y/?] (NEW) n
CRC32 functions (CRC32) [Y/?] y
CRC32c (Castagnoli, et al) Cyclic Redundancy-Check (LIBCRC32C) [M/n/y/?] m
:0: sorry, unimplemented: 64-bit mode not compiled in
:0: sorry, unimplemented: 64-bit mode not compiled in
  SPLIT   include/linux/autoconf.h -> include/config/*
  CC      scripts/mod/empty.o
scripts/mod/empty.c:1: sorry, unimplemented: 64-bit mode not compiled in
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make: *** [scripts] Error 2

!!! ERROR: cross-i686-pc-linux-gnu/linux-headers-2.6.11 failed.
!!! Function compile_headers, Line 363, Exitcode 2
!!! prepare failed
!!! If you need support, post the topmost build error, NOT this status message.
Comment 8 SpanKY gentoo-dev 2005-04-15 15:09:55 UTC
yes, eradicator and i discussed how the new amd64/2005.0/multilib stuff with CFLAGS_abi breaks cross-compiling pretty bad

the workaround for now is to try `export ABI="EATME"` i think ...
Comment 9 SpanKY gentoo-dev 2005-07-28 13:22:37 UTC
crossdev exports a bogus ABI variable now since the stupid amd64 profile keeps
forcing amd64 by default and no one is interested in fixing the situation any
time soon