Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ESE Key Daemon 1.2.4: FTBFS with gcc-4.5
Date: Sat, 09 Apr 2011 19:28:43 -0700	[thread overview]
Message-ID: <4DA115DB.1000209@gmail.com> (raw)
In-Reply-To: <BANLkTimD2hxAA-nQPGFzUhXtJLzVXui1Jg@mail.gmail.com>

On 4/6/2011 4:34 AM, Luís Filipe Salé Borlido wrote:
> Hi!
>
> I was compiling a new image for mini2440  that contains esekeyd and I got an
> error:
>
> NOTE: Running task 2457 of 4369 (ID: 199,
> /opt/OpenEmbedded/openembedded/recipes/esekeyd/esekeyd_1.2.4.bb, do_compile)
> NOTE: package esekeyd-1.2.4-r0: task do_compile: Started
> ERROR: Logfile of failure stored in:
> /opt/OpenEmbedded/build/tmp/work/armv4t-angstrom-linux-gnueabi/esekeyd-1.2.4-r0/temp/log.do_compile.11553
> Log data follows:
> | + do_compile
> | + base_do_compile
> | + '[' -e Makefile -o -e makefile -o -e GNUmakefile ']'
> | + oe_runmake
> | + oenote make
> | + echo NOTE: make
> | NOTE: make
> | + make
> | make  all-recursive
> | make[1]: Entering directory
> `/opt/OpenEmbedded/build/tmp/work/armv4t-angstrom-linux-gnueabi/esekeyd-1.2.4-r0/esekeyd-1.2.4'
> | Making all in src
> | make[2]: Entering directory
> `/opt/OpenEmbedded/build/tmp/work/armv4t-angstrom-linux-gnueabi/esekeyd-1.2.4-r0/esekeyd-1.2.4/src'
> | arm-angstrom-linux-gnueabi-gcc -march=armv4t -mtune=arm920t
> -mthumb-interwork -mno-thumb
> --sysroot=/opt/OpenEmbedded/build/tmp/sysroots/armv4t-angstrom-linux-gnueabi
> -DHAVE_CONFIG_H -I. -I..     -fexpensive-optimizations -fomit-frame-pointer
> -frename-registers -O2 -ggdb2 -MT keytest.o -MD -MP -MF .deps/keytest.Tpo -c
> -o keytest.o keytest.c
> | keytest.c: In function 'main':
> *| keytest.c:55:3: error: variable-sized object may not be initialized*
> | make[2]: *** [keytest.o] Error 1
> | make[2]: Leaving directory
> `/opt/OpenEmbedded/build/tmp/work/armv4t-angstrom-linux-gnueabi/esekeyd-1.2.4-r0/esekeyd-1.2.4/src'
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory
> `/opt/OpenEmbedded/build/tmp/work/armv4t-angstrom-linux-gnueabi/esekeyd-1.2.4-r0/esekeyd-1.2.4'
> | make: *** [all] Error 2
> | + die 'oe_runmake failed'
> | + oefatal 'oe_runmake failed'
> | + echo FATAL: 'oe_runmake failed'
> | FATAL: oe_runmake failed
> | + exit 1
> NOTE: package esekeyd-1.2.4-r0: task do_compile: Failed
> ERROR: Function 'do_compile' failed (see
> /opt/OpenEmbedded/build/tmp/work/armv4t-angstrom-linux-gnueabi/esekeyd-1.2.4-r0/temp/log.do_compile.11553
> for further information)
> ERROR: Task 199 (/opt/OpenEmbedded/openembedded/recipes/esekeyd/
> esekeyd_1.2.4.bb, do_compile) failed with exit code '1'
> ERROR: '/opt/OpenEmbedded/openembedded/recipes/esekeyd/esekeyd_1.2.4.bb'
> failed
>
> In one of the Debian bug reports (
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564981), they seem to say
> that the package cannot be built using gcc-4.5, which is the version of
> arm-angstrom-linux-gnueabi-gcc that is being used to build the package.
>
> To solve this problem I added a recipe to esekeyd-1.2.7 (in attach) and now
> it's working.
>

can you resend the patch following submission guidelines
http://openembedded.org/index.php/How_to_submit_a_patch_to_OpenEmbedded
> Best regards,
> Luís Borlido
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




      reply	other threads:[~2011-04-10  2:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTimy1b_JM5zx9EYJddfEqk4MYWZ2Pg@mail.gmail.com>
2011-04-06 11:34 ` ESE Key Daemon 1.2.4: FTBFS with gcc-4.5 Luís Filipe Salé Borlido
2011-04-10  2:28   ` Khem Raj [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DA115DB.1000209@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox