summaryrefslogtreecommitdiff
path: root/packages/gcc/gcc_3.4.4.bb
AgeCommit message (Collapse)AuthorFiles
2005-09-22gcc_3.4.4: updated thumb patchesJohn Bowler1
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.
2005-09-10gcc_3.4.4: fix the native build on ucslugc by using arm, not thumbJohn Bowler1
For some reason a thumb built gcc 3.4.4 fails to produce functional executables even when linked dynamically (i.e. even when next to none of the code in the resultant executable comes from the compiler itself). This requires further investigation (or maybe the csl gcc), this commit changes the build to generate arm even on thumb systems as a temporary fix.
2005-09-09gcc(libgcc_s.so.1): fix the arm interwork _call_via_rX out of line opsJohn Bowler1
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.
2005-09-07gcc-3.4.4, openzaurus-3.5.4: remove DEFAULT_PREFERENCE from gcc bb files and ↵Justin Patrin1
use PREFERRED_VERSION in openzaurus conf to force use of gcc 3.4.4
2005-09-07gcc_3.4.4: add DEFAULT_PREFERENCE_arm-linux to replace same removed from gcc_cslJustin Patrin1
2005-08-11This set of changes ensures that TARGET_CC_ARCH is passed reliably to allJohn Bowler1
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.
2005-07-23Add symlink to cpp, so package cpp-symlinks actually gets createdDavid Karlstrom1
2005-06-30import clean BK tree at cset 1.3670Koen Kooi1
2005-06-03Merge bk://oe-devel.bkbits.net/openembeddednslu2-linux.adm@bkbits.net1
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