Matthias Fuchs | 10 Dec 20:19 2014
Picon

complete sources for ELDK target images

Hi,

what's the best way to collect all sourcecode and licenses that are
involved in an ELDK/yocto based target image? So that these files can be
used to provide the complete sourcecode for a given target (in order to
fulfill license demands)

One method could be to provide the ELDK git repository and the download
directory that is created during the build process. But this contains
more sources than are required to build a special target image (also
contains toolchain and other images releated files).

The installed_pkgs.txt file only lists the package names and not the
sources itself.

I expect this to be a common task when creating yocto based products.
But I did not find the best way so far.

Matthias
Albrecht Dreß | 2 Dec 20:44 2014
Picon

ELDK & Coverage Analysis

Hi all,

I use ELDK 5.4 for a MPC5200 based board, and would like to run unit tests with a coverage analysis.

I see that powerpc-linux-gcov is included, but building for a coverage analysis results in

powerpc-linux-gcc -g -O -fprofile-arcs -ftest-coverage tests.c -o
tests
/opt/eldk-5.4/powerpc/sysroots/i686-eldk-linux/usr/libexec/powerpc-linux/gcc/powerpc-linux/4.7.2/ld:
cannot find -lgcov

On my Ubuntu system I can run gcov for the same test app.  Did I miss to install some package from ELDK, or do I
have to build the necessary "infrastructure" myself?

Thanks,
Albrecht.
_______________________________________________
eldk mailing list
eldk@...
http://lists.denx.de/mailman/listinfo/eldk
Larry Baker | 12 Nov 20:57 2014
Picon

Re: Cross Compile newer bash rpm for eldk (for ppc-v42-1)

Adir,

I did not see your original post, so I do not know what errors you encountered.  (I do not understand why you are
using a CentOS source RPM for a PPC CPU.)  However, it should be possible to update an old bash to patch the
ShellShock vulnerability.  I have done it on several of our CentOS and Mac OS X systems that are many years
old.  I recommend that you stick with the version of bash your system already uses, apply the latest patches
to that release, and build that.  On your target system, enter "bash --version" to display the version.  For
example, on my Mac OS X 10.6 system, the version is 3.2.X.  You can download the GNU sources and patches for
that version directly from https://ftp.gnu.org/pub/gnu/bash.  Alternately, if you have the sources
for the version you are running (ELDK v4.2), all you will need are the patches since that release.  I think in
either case you will have to apply the patches you need manually.  If you use the GNU sources, there is a
configure command that will hopefully create a makefile you can use.  If you are patching the ELDK v4.2
sources, follow the ELDK instructions to update an application.

For example, for the Mac OS X 10.6 bash, I performed these steps after I determined I needed patches 052
through 057 (which was the latest patch at the time):

• Download the patch files from gnu.org. These must start with bash32-052, and include
     all subsequent patches sequentially:

  $ for patch in 052 053 054 055 056 057
    do
       curl -O https://ftp.gnu.org/pub/gnu/bash/bash-3.2-patches/bash32-${patch}
    done

• Apply the patches in order:

  $ cd bash-92/bash-3.2
  $ for patch in 052 053 054 055 056 057
    do
(Continue reading)

Wolfgang Denk | 12 Nov 17:42 2014
Picon
Picon

Re: Cross Compile newer bash rpm for eldk (for ppc-v42-1)

Dear Adir,

In message
<db100343705343de912bfd7f086bd141@...>
you wrote:
>
> I'm trying to build new rpm for eldk4.2 for ppc460 cpu.
> 
> I failed while I'm building the source rpm version http://vault.centos.org/
> 6.5/updates/Source/SPackages/bash-4.1.2-15.el6_5.2.src.rpm

This is pretty normal, I'm afraid.  ELDK v4.2 was based on bash 3.2 of
May, 2007 - that's more than 7 years ago.   You must not expect that
you can just update to pretty recent versions of some software
package any more.  You will find that you run into a dependency here
and one there, which in turn will cause other dependencies, and in a
blink of an eye you will be trapped in a maze of depencencies which
cover more or less the whole distribution.

ELDK v4.2 is outdated, and it is practically impossible to update it.

It was a great release - I think the best we ever did - but now it is
obsolete, and time to move on.

I recommend you stop wasting your time on that old stuff, and switch
to a more recent ELDK v5.x version.

Best regards,

Wolfgang Denk
(Continue reading)

Picon

Re: U-Boot compile with error

Hi Wolfgang

After your response I tried exactly the same as you using:

eldk-switch -m -r 5.5 armv7a

It gives:

eldk-switch.sh: ELDK 5.5 for armv7a is not installed!

and 

eldk-switch -l 

gives: 

+--- Installed ELDK versions:

I think there is a problem with the installation of the ELDK. I installed the ELDK in an other path as /opt/eldk5.5

Do you think this may be the reason of the compiler (linker) issue?

Thanks

Ludo

----Ursprüngliche Nachricht----
Von : wd <at> denx.de
Datum : 28/10/2014 - 20:37 (CET)
An : l.heusser <at> bluewin.ch
(Continue reading)

Wolfgang Denk | 28 Oct 21:31 2014
Picon
Picon

Re: U-Boot compile with error

Dear Ludo,

please keep the ML on Cc:.

In message
<10558951.48793.1414527047766.JavaMail.webmail@...>
you wrote:
> 
> After your response I tried exactly the same as you using:
...
> It gives:
> eldk-switch.sh: ELDK 5.5 for armv7a is not installed!
> and 
> eldk-switch -l 
> gives: 
>
> +--- Installed ELDK versions:
>
> I think there is a problem with the installation of the ELDK. I installed the ELDK in an other path as /opt/eldk5.5

Only "eldk-switch" should be affected by this; you would have to adapt
it's configuration for your alternate installation directory.

> Do you think this may be the reason of the compiler (linker) issue?

I don't think so.

Can you please provide the exact commands you have been using which
lead to that error?

(Continue reading)

Picon

U-Boot compile with error

Hello
I try to build u-boot (mainline) using the ELDK 5.5 for Beaglebone Black but the build compile with error.
Here the end of the build output:
  AS      arch/arm/cpu/armv7/start.o
  AS      arch/arm/cpu/armv7/omap3/lowlevel_init.o
  LD      arch/arm/cpu/armv7/omap3/built-in.o
  CC      common/main.o
  CC      common/board_f.o
  CC      common/cmd_version.o
  LD      common/built-in.o
  CC      drivers/usb/gadget/f_fastboot.o
  LD      drivers/usb/gadget/built-in.o
  CC      lib/display_options.o
  LD      lib/built-in.o
  LD      examples/standalone/hello_world
arm-linux-gnueabi-ld.bfd: cannot find -lgcc
make[2]: *** [examples/standalone/hello_world] Error 1
make[1]: *** [examples/standalone] Error 2
make: *** [examples] Error 2
Can anybody help? Thanks
Ludo
_______________________________________________
eldk mailing list
eldk@...
http://lists.denx.de/mailman/listinfo/eldk
Wolfgang Denk | 27 Oct 19:59 2014
Picon
Picon

Re: eldk-5.5.2 issues

Dear Albrecht,

In message <1414433699.5968.2 <at> deneb.(none)> you wrote:
>
> Just to understand your statement correctly: do you recommend to use
> ELDK 5.4 for the PowerPC instead of ELDK 5.5.x (I'm working with the
> Freescale MPC5200 and the QorIQ P2020 processors)?

I have to admit that I am not in a position yet to give any
recommendations based on deeper knowledge or understanding;
I cannot even tell if the observed effects are known GCC bugs, or if
the fact that the same effects are no longer present in 4.9.1 is
because a bug was detected and fixed, or just by pure chance.

> Does this apply to the kernel only, or also to user-space software,
> or to u-boot?

THis applies at least to U-Boot and Kernel, or more generaly to all
kinds of code where you take special efforts when arranging things
like the stack layout and/or the image linking.

I got bitten (on a MPC5200 by the way) by the fact that GCC 4.8.x
fails to provide relocation information for symbols in the (new)
.data.rel.ro and .data.rel.ro.local segments.  You could call this a
deciciency in the U-Boot linker scripts, but then, it got "fixed" (or
changed again) in gcc 4.9.1.  For details, see [1] and [2].

The ARM Linux kernel folks even discuss blacklisting GCC 4.8.x for
other reasons, see [3]

(Continue reading)

Pavel Machek | 23 Oct 16:51 2014
Picon
Picon

eldk-5.5.2 issues

Hi!

Eldk-5.5 seems to miscompile u-boot on altera socfpga (arm board), so
I tried updating to eldk-5.5.2... but I ran into problems compiling
u-boot-mkimage.

Does that work for you?

I did cleanall, still I'm getting "object directory ... does not
exist". I guess rm -rf /opt/eldk/downloads/ would solve that, but
perhaps there's solution not involving excessive force?

include/stddef.h is missing. Should more dependencies be added to
u-boot-mkimage recipe?

Eldk-5.5 compilation works ok for me.

Best regards,
								Pavel

| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 CROSS_COMPILE= HOSTCC=gcc  HOSTLD=ld
| HOSTLDFLAGS=-L/opt/work/pavel/build-wagabuibui/tmp/sysroots/x86_64-linux/usr/lib
| -L/opt/work/pavel/build-wagabuibui/tmp/sysroots/x86_64-linux/lib
| -Wl,-rpath-link,/opt/work/pavel/build-wagabuibui/tmp/sysroots/x86_64-linux/usr/lib
| -Wl,-rpath-link,/opt/work/pavel/build-wagabuibui/tmp/sysroots/x86_64-linux/lib
| -Wl,-rpath,/opt/work/pavel/build-wagabuibui/tmp/sysroots/x86_64-linux/usr/lib
| -Wl,-rpath,/opt/work/pavel/build-wagabuibui/tmp/sysroots/x86_64-linux/lib
| -Wl,-O1 HOSTSTRIP=true CONFIG_MX28=y tools
| error: object directory
(Continue reading)

Anatolij Gustschin | 8 Oct 15:09 2014
Picon
Picon

[ELDK-5.3 PATCH] meta-eldk: bash: add updates and recent 'Shellshock' fixes

Some projects still use Danny based ELDK-5.3, so add bash updates.
Taken from Chris Tapp's meta-danny-maintenance layer and updated
with recent bash fixes.

Signed-off-by: Anatolij Gustschin <agust@...>
---
 meta-eldk/recipes-extended/bash/bash_4.2.bbappend |  140 +++++++++++++++++++++
 1 file changed, 140 insertions(+)
 create mode 100644 meta-eldk/recipes-extended/bash/bash_4.2.bbappend

diff --git a/meta-eldk/recipes-extended/bash/bash_4.2.bbappend b/meta-eldk/recipes-extended/bash/bash_4.2.bbappend
new file mode 100644
index 0000000..4523d25
--- /dev/null
+++ b/meta-eldk/recipes-extended/bash/bash_4.2.bbappend
 <at>  <at>  -0,0 +1,140  <at>  <at> 
+# Update the patch level of bash 4.2
+#
+# Created: 2014-09-28 to fix 'Shellshock' vulnerabilities
+
+# Make sure the PR gets 'bumped' so that use of this append after the base recipe has
+# been built will result in a rebuild.
+PRINC := "${ <at> int(PRINC) + 1}"
+
+SRC_URI_append = " \
+    ${GNU_MIRROR}/bash/bash-4.2-patches/bash42-011;apply=yes;striplevel=0;name=patch011 \
+    ${GNU_MIRROR}/bash/bash-4.2-patches/bash42-012;apply=yes;striplevel=0;name=patch012 \
+    ${GNU_MIRROR}/bash/bash-4.2-patches/bash42-013;apply=yes;striplevel=0;name=patch013 \
+    ${GNU_MIRROR}/bash/bash-4.2-patches/bash42-014;apply=yes;striplevel=0;name=patch014 \
+    ${GNU_MIRROR}/bash/bash-4.2-patches/bash42-015;apply=yes;striplevel=0;name=patch015 \
(Continue reading)

Marek Vasut | 9 Aug 16:13 2014
Picon
Picon

Please update ELDK 5.5.x to 5.5.2

Hello all,

I am getting reports about occasional kernel crashes on ARMv7 [3]. I found out 
this is caused by GCC bug [1], resolved in Yocto 1.5.2 [2] and thus ELDK 5.5.2 . 
The git commit ID in Yocto and ELDK is 97c9163d97911dad0afcd0dae39e5c426e27e921 
. To prevent being affected by this bug, please update your ELDK 5.5.x to ELDK 
5.5.2 or newer.

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854
[2] 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dora&id=97c9163d97911dad0afcd0dae39e5c426e27e921

[3] This is the backtrace caused by the bug. Please note that the PC is pointing 
to 'find_get_entry' function, which is miscompiled by the GCC 4.8.x without the 
patch:
--8<--
Unable to handle kernel paging request at virtual
address ffffffff
pgd = be138000
[ffffffff] *pgd=4fffd821, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1] SMP ARM
Modules linked in:
CPU: 0 PID: 31055 Comm: ip Not tainted 3.15.0+ #8
task: be2f4440 ti: be3e4000 task.ti: be3e4000
PC is at find_get_entry+0x5c/0xf8
LR is at radix_tree_lookup_slot+0x1c/0x2c
pc : [<800a6380>]    lr : [<802a3580>]    psr: a0000113
sp : be3e5ce8  ip : 00000000  fp : be3e5d1c
r10: a0000113  r9 : be8c4c80  r8 : 00000002
r7 : bed84558  r6 : 00000001  r5 : 00000000  r4 : bed84428
(Continue reading)


Gmane