| Age | Commit message (Collapse) | Author | Files |
|---|
|
have been 'CPP'. I have tested build for gcc-cross-4.2.2 recipe.
|
|
everyone, not just as a slugos specific override.
|
|
gcc-configure-{target|cross|sdk} and a common include file. Factor some common data not related to configure into gcc-common.inc. Rewrite 3.3.3 and 3.3.4 recipes to use standard includes (tested and they work).
|
|
everything needed
|
|
|
|
|
|
|
|
lower. There should be no functionality change yet, it just makes that change easier to remove target packaging from cross builds
|
|
these
|
|
fixes the sdk version to use the correct sysroot which is important for ease of use of SDKs and standalone toolchains. This change means a gcc rebuild unfortunately
|
|
* Accept arm926ej-s, arm1026ej-s for -mtune=, as that's what we have in OE.
|
|
|
|
bump PR to make sure gcc-cross reinstalls after cross changes to ensure everything works correctly
|
|
applied changes from 515587ac4598d7ab78bd946632a31cf94fa79bf8 (.oz354x)
through 33d804e082e0702e05818192cfab8a8610605d88
|
|
|
|
The four previous thumb related patch files have been combined into one
and simplified. Additional problems with call_via_rX functions being
called via the PLT have been fixed (the functions can no longer be called
this way - they are hidden). Unnecessary adds of exports of these
functions from libgcc have been removed.
|
|
The interworking symbols were being built but not exported from libgcc
(i.e. they were not in the version file), added a specific version file
for them and updated t-linux. Forced the cross build to always generate
ARM instructions (the thumb version does not currently work), bumped
PRs.
|
|
use PREFERRED_VERSION in openzaurus conf to force use of gcc 3.4.4
|
|
|
|
packages in a build. The change fixes problems in the following packages:
binutils{,-cross}_2.15.94.0.1
HOST_CC_ARCH was not being passed to HOST_CC. The problem does
not seem to be present in binutils* 2.16, however this version
is still used for uClibc builds.
gcc{,-cross,-cross-initial}_3.4.4
HOST/TARGET_CC_ARCH was not used in the appropriate places, plus
this was not sufficient - FLAGS_FOR_TARGET (a gcc make variable)
is now preloaded with the target CC_ARCH values, which causes all
the builds (gcc, g++, gcj, fortran) to get the correct values.
gcc OTHER
*NOT* fixed - other versions of gcc will still need the _CC_ARCH
fix in the same lines (CC_FOR_TARGET, GCC_FOR_TARGET, CXX_FOR_TARGET),
however so long as these builds use gcc3-*.inc the FLAGS_FOR_TARGET
fixx will be there.
uclibc{,-initial}_0.9.27
TARGET_CC_ARCH added to the do_compile. For the do_stage step the
build actually compiles target code (make utils), but this will not
accept a CC with whitespace. The TARGET_CC_ARCH flags have therefore
been added to CFLAGS (a bit ugly, but it works).
These changes have been tested for both cross and target builds, the changes
should be fine on self-hosted (i.e. target-hosted) builds, if anyone actually
does these, but note that the gcc build specifically tests for build==host and
does *not* do certain _FOR_TARGET settings in this case (this was the case
before this change too) - if you are seeing strange settings on self-hosted
gcc builds (before and after this change) check the do_compile environment
variable settings.
|
|
|
|
into bkbits.net:/repos/n/nslu2-linux/openembedded
2005/06/03 09:15:57+01:00 reciva.com!pb
also provide -cross-initial version of gcc 3.4.4
2005/06/03 08:47:26+01:00 reciva.com!pb
update gcc (3.4 branch) to 3.4.4
BKrev: 42a01769rMtsZgasmLeQNvdzr2RGLA
|
