John Bowler [Fri, 12 Aug 2005 18:32:06 +0000 (18:32 +0000)]
monotone-5 0.22 - the LUA hook for anonymous_read must be updated (moved
into the standard read hook).
test 247 (lua function existsonpath) fails - apparently there is a problem
with search the path for executables. This is the only remaining
unexpected failure (all unexpected failures in previous versions except the
netsync 'largish-file' test now function correctly on an NSLU2).
John Bowler [Fri, 12 Aug 2005 15:09:06 +0000 (15:09 +0000)]
nslu2.conf: change to the IPKG_ARCHS to include the correct architectures
(armv*b for all armv* suppported by the xscale processor). The old
'generic' armeb is still suppported (of course) and, by default, this is
the ARCH of the generated packages - this is technically wrong, the
packages are actually armv5teb - but changing this would make the feeds
non-functional for existing systems.
Holger Freyther [Thu, 11 Aug 2005 22:02:40 +0000 (22:02 +0000)]
packages/uicmoc/uicmoc3-native_3.3.2.bb:
-If the package is named uicmoc, install uic and moc
do not stage static libaries and do to stage the header files.
There is a reason we have qt2 and qt3 dir in staging and this
is not because uicmoc3 can stage its Qt3 headers into STAGING_INCDIR
directly.
--cookies for some one...
John Bowler [Thu, 11 Aug 2005 20:49:14 +0000 (20:49 +0000)]
Change the NSLU2 kernel build configuration method to allow the
configuration override to be specified in the machine.conf rather than
hardwiring -mno-thumb-interwork into nslu2-kernel.inc
John Bowler [Thu, 11 Aug 2005 20:28:39 +0000 (20:28 +0000)]
mpd was building, but not necessarily using, it's own local cache of the
libmad and libid3tag source. Removing the --enable-mpd-* settings causes
it not to build the local source (and it uses the versions in staging).
John Bowler [Thu, 11 Aug 2005 20:03:56 +0000 (20:03 +0000)]
This set of changes ensures that TARGET_CC_ARCH is passed reliably to all
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.
John Bowler [Thu, 11 Aug 2005 16:57:39 +0000 (16:57 +0000)]
ucslugc, UCSLUGC_PACKAGES: make various prerequesite packages explicit in
the build list, therefore if the dependent package is removed the
prerequisite packages are still built.
Michael Lauer [Tue, 9 Aug 2005 23:08:49 +0000 (23:08 +0000)]
Third (and hopefully last) EFL revamp before I hand over maintainership to
Justin Patrin. We now have a efl.bbclass that contains common code for the
various libraries. This makes it possible to have very clean and concise bb's.
Holger Freyther [Tue, 9 Aug 2005 21:32:11 +0000 (21:32 +0000)]
oe/packages/qte/qte_2.3.10.bb:
oe/packages/opie-buttons-settings/opie-button-settings.inc:
-Remove the ASUS support as there will be no asus machine
in oe.