Age | Commit message (Collapse) | Author | Files |
|
* aka "generic pxa270 config"
|
|
|
|
* builds for angstrom/ixp4xxbe
* other distros and machines need to add their own uClibc.machine and uClibc.distro configs
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Since the default now for x86 target is arch=i486 this is need for uclibc to build
Bump PR
|
|
|
|
Since the default now for x86 target is arch=i486 this is need for uclibc to build
|
|
|
|
|
|
|
|
|
|
|
|
Add patch to allow gettext to compile
|
|
|
|
|
|
see email thread at http://lists.openembedded.org/pipermail/openembedded-devel/2006-October/000523.html for details
|
|
|
|
* OE's strip functionality can't cope with a debugbuild of uclibc yet, so beware
|
|
* inspired by Richards code from linux-openzaurus.inc
|
|
the OE/uclibc people are displaying for patches sent to the mailinglist, this could break for some configurations
|
|
|
|
|
|
|
|
|
|
(patches derived from busybox mailing list)
|
|
http://busybox.net/lists/uclibc-cvs/2006-January/008903.html
|
|
Use require for the BitBake files within packages. In contrast
to the conf files the authors of these files expected these files
to be included.
|
|
compile errors (from Stelios Koroneos)
|
|
|
|
- since they do apparently work (however 20060120, against these patches
have been tested, produces non-working shells such as busybox ash and
bash.)
|
|
- this updates the patch set to svn 20060120, the patches now apply
but the result is non-functional (completely).
|
|
- rather than build nslu2-kernel or nas100d-kernel slugos-image now
builds ixp4xx-kernel, the generic kernel. ixp4xx is now used as the
normal MACHINE override, even though MACHINE itself is still set to
nslu2 or nas100d (or ixp4xx).
|
|
x.x.x+cvsYYYYMMDD format and some includes some minor whitespace cleanup.
|
|
- the file is actually used in all NSLU2 uclibc builds, even though
- it contains distro settings, therefore to avoid replicating it it
- is made the default for all NSLU2
|
|
- Change uclibc 0.9.28 ucslugc builds (only) to use the new mechanism
- to select ucslugc arm and armeb config
- There is no change to any build config (including ucslugc), just a
- change in mechanism.
|
|
This, together with the fixes in gcc and binutils, allows a system to
be build with thumb libgcc and libuClibc (etc). ucslugc is changed to
release 2 and to use thumb compilation of these modules.
|
|
these packages
This commit causes thumb build for everything in ucslugc-packages except
these packages and libgcc (from gcc). libgcc and uclibc still need some
work, the other packages reveal compiler bugs (monotone), source bugs
(alsa) or missing configuration (thumb arch support in util-linux) and so
are disabled for the moment.
|
|
The SVN version now copies 0.9.28 patches, the armeb case should work,
other architectures almost certainly require the uclibc-cvs/*/uClibc.config
copy of the config file to be deleted (if this is done the build will pick
up the config file in uclibc-0.9.28).
|
|
STT_ARM_TFUNC handling was broken in uclibc because it is an ARM specific
hack and uclibc code did not have support for it. Added the support in a
way which I hope will be acceptable to uclibc and which should remain
compatible with forthcoming binutils changes. ARM Thumb code is fully
working with this commit with the possible exception of uclibc/gcc itself
(not yet tested).
|
|
Some of the thumb patches had already been pushed into the uclibc release,
this commit adds corrected/updated versions of most of the ones which had
not been accepted. The controversial 'change the ldso symbol resolver'
patch is not in this set - it will be re-worked to match the changes being
made in binutils for the same problem.
|
|
The config now sets the processor option to XScale, correct for ucslugc
(which is NSLU2)
|
|
IMPORTANT: the uClibc dynamic loader has changed in this release, the
startup and finalisation is changed and this requires applications to
be rebuilt with the new uclibc. If this is not done the applications
will not work correctly.
uclibc 0.9.28 contains all the non-thumb (ARM instruction set) patches
OE applied to 0.9.27, this check in includes minimal updates to the
uClibc.config file for each machine architecture, maintainers of
individual architectures may want to make more changes to take advantage
of new features in uClibc.
It is possible to configure uClibc to offer backward compatibility with
the 0.9.27 dynamic loader, if this is done it will still be necessary to
have both uClibc DLLs (0.9.27 and 0.9.28) on the system for un-recompiled
applications to build. This commit does *not* do this.
With this commit the uclibc build is running the 'fix_includes.sh' script
to verify the cross build header files. This seems to function correctly
however it is possible that some distros may have incorrect header files
(particular if uclibc-initial is built) - in that case it will be
necessary to re-introduce the nokernelheader.patch
If it is necessary to continue to use 0.9.27 in the presence of this
upgrade set PREFERRED_VERSION_uclibc in the DISTRO .conf file.
|
|
specific string asm in uclibc it is possible to run at least some thumb
executables on ucslugc. The changes can be incorporated into other
distros by setting thumb-interwork in OVERRIDES - the changes do change
the way ARM code executes (necessarily). (Changes have also been submitted
as bug 385 to uclibc.org).
|
|
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.
|
|
|