| Age | Commit message (Collapse) | Author | Files |
|---|
|
|
|
* siteinfo.bbclass, bfin-common: autofoo support
* kernel-arch.bbclass, linux-libc-headers_2.6.20.bb: bfin -> blackfin mapping for the kernel
* insane.bbclass: stubs for bfin arch, needs proper number, but that will get reported when it encounters the first binary
* uclibc: config for adsp-bf537-stamp machine
* adsp-bf537-stamp.conf: machine description for adsp-bf537-stamp board (http://www.analog.com/en/prod/0%2C2877%2CBF537%25252DSTAMP%2C00.html)
The build currently stops in binutils cross with the "ld not supported on this archicture" message
|
|
|
|
|
|
characters. Closes bug #2227
|
|
|
|
|
|
|
|
WORKDIR and STAGING
[18:23] likewise: would be my proposed fix for now, until we figure out if cross tooling need to RPATH to it's own libs.
|
|
occurences.
|
|
|
|
the file path.
|
|
|
|
|
|
fixes in the shared library handling.
|
|
|
|
gcc-cross-sdk)
|
|
|
|
|
|
rsplit was introduced in python 2.4 and is like split but starts to
split from the right side. The only difference is obviously if you
have maxsplit set (which we don't). So it is fine to remove the 'r'
|
|
sed out /usr/include references
|
|
add bb.fatal
udev has a link to host binaries, do not check the architecture
of these binaries. We will skip all links for now for the two
reasons:
-We either point to a file in our package and then we will
check it anyway
-It is a file for a another package, which will be checked
anyway
Make architecture mismatch a fatal/insane error and return False.
This should fix the issue koen has seen when he added a bb.fatal
the make_fatal_error method returns true if the error should be
made fatal, in this case our checks need to set sane to False.
The return not makes sure this is happening.
|
|
arguments for format string by removing a spurious '%s'
|
|
Added extra entry into dict to mark 32bit/64bit and use it for manipulating
ELF headers.
Some architectures would need checking (not OE ones).
|
|
|
|
|
|
|
|
The idea of insane.bbclass is to report all issues found at
once. This is why the checks return True if no error was found
and False if at least one was found.
At the end of all check runs we will see if at least one check
failed and call bb.fatal
|
|
so do bb.fatal instead if bb.error
symptom:
ERROR: Architecture did not match (20 to 3) on /work/ppc603e-angstrom-linux/udev-092-r15/install/udev/sbin/scsi_id
This means OE detected type 3 (i386) while it expected type 20 (powerpc), most likely caused by some fool hardcoding 'gcc' as compiler
|
|
|
|
|
|
native ones:
.la files should have installed=yes (at least I believe
this). And somehow some believe this as well, some don't though...
some like fakeroot love to install two .la files...
non-native:
.la should have installed=no
both:
should not point to tmp/work. libgettext and libltdl(libtool)
fails this...
happy fixing and arguing
|
|
r1258,r1195)
The .so check now looks for symlinks ending with .so. These are a typical
trait of -dev packages and kills a lot of false positives.
This was authored by ross and was taken from the poky svn repository.
|
|
|
|
|
|
* change "," to "%" so python doesn't die if an error occurs
* spell architecture correctly
* add arm/eabi tupple that works for stripped binaries, but fails for -dbg binaries (abiversion 0 vs 97)
|
|
Debian packages
|
|
x86_64 can not be detected properly with this code - needed change:
- ELFFile.my_assert(self.data[ELFFile.EI_CLASS], chr(ELFFile.ELFCLASS32)) # only 32 bits
+ ELFFile.my_assert(self.data[ELFFile.EI_CLASS], chr(ELFFile.ELFCLASS64))
|
|
|
|
Add a small ELF parser and read OSABI, ABIVERSION, ENDIAN and MACHINE. This
code compares TARGET_OS and TARGET_ARCH to a list of known versions. Currently
we have values for linux and linux-uclibc for arm, armeb and powerpc. mips,
i386, amd64, ia64 are missing. ABI wise ARM EABI is missing as well, but koen
is likely to enter the values into the documented dict
|
|
Add a method to implement koen's skipping of
errors of type .so in non dev package. This
will turn into a list of known and acked issues which
we decided to ignore. I do not yet know how to maintain
such a list properly though
Split the .so in non-dev package and the .debug in non-dbg
package into two different packages
|
|
-Print all errors of the built packages and if we have printed
any errors fail
-Log the errors to a log file, so we can see them afterwards
-Print the path (- the TMPDIR) of the package in question
|
|
errors
-Inspired by doku's work on mpd's buildsystem grep through
the config.log and find broken autotools tests
-Make errors fatal so we will notice these things more quickly.
|
|
mailing list. There should be no functionality changes yet.
|
|
|
|
|
|
|
|
Untested check inspired by Richard to check if non debug packages
depends on -dbg packages.
|
|
|
|
Holger F.
|
