Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jens Rehsack <rehsack@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Should openssl(-native) build-depends on perl-native?
Date: Mon, 05 Oct 2015 09:12:21 +0100	[thread overview]
Message-ID: <1444032741.5118.5.camel@linuxfoundation.org> (raw)
In-Reply-To: <9EEC2D18-21A2-40BA-97B3-D8DD67015AC9@gmail.com>

On Sat, 2015-10-03 at 14:51 +0200, Jens Rehsack wrote:
> I hit a build error never seen before:
> 
> | gcc  -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN     -DTERMIO -isystem/home/sno/fsl-community-bsp/ornithologen-kann-man-mit-voegeln-eine-freude-machen/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -Wall -Wa,--noexecstack -DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -isystem/home/sno/fsl-community-bsp/ornithologen-kann-man-mit-voegeln-eine-freude-machen/tmp/sysroots/x86_64-linux/usr/include  -c -o sha512.o sha512.c
> | /home/sno/perl5/perlbrew/perls/perl-5.6.2/bin/perl asm/sha1-x86_64.pl elf > sha1-x86_64.s
> | Can't locate bigint.pm in @INC (@INC contains: /home/sno/perl5/perlbrew/perls/perl-5.6.2/lib/5.6.2/x86_64-linux /home/sno/perl5/perlbrew/perls/perl-5.6.2/lib/5.6.2 /home/sno/perl5/perlbrew/perls/perl-5.6.2/lib/site_perl/5.6.2/x86_64-linux /home/sno/perl5/perlbrew/perls/perl-5.6.2/lib/site_perl/5.6.2 /home/sno/perl5/perlbrew/perls/perl-5.6.2/lib/site_perl .) at asm/../../perlasm/x86_64-xlate.pl line 200.
> | BEGIN failed--compilation aborted at asm/../../perlasm/x86_64-xlate.pl line 200.
> | make[2]: *** [sha1-x86_64.s] Error 141
> | make[2]: Leaving directory `/home/sno/fsl-community-bsp/ornithologen-kann-man-mit-voegeln-eine-freude-machen/tmp/work/x86_64-linux/openssl-native/1.0.2d-r0/openssl-1.0.2d/crypto/sha'
> | make[1]: *** [subdirs] Error 1
> | make[1]: Leaving directory `/home/sno/fsl-community-bsp/ornithologen-kann-man-mit-voegeln-eine-freude-machen/tmp/work/x86_64-linux/openssl-native/1.0.2d-r0/openssl-1.0.2d/crypto'
> | make: *** [build_crypto] Error 1
> | ERROR: oe_runmake failed
> | WARNING: /home/sno/fsl-community-bsp/ornithologen-kann-man-mit-voegeln-eine-freude-machen/tmp/work/x86_64-linux/openssl-native/1.0.2d-r0/temp/run.do_compile.15132:1 exit 1 from
> |   exit 1
> | ERROR: Function failed: do_compile (log file is located at /home/sno/fsl-community-bsp/ornithologen-kann-man-mit-voegeln-eine-freude-machen/tmp/work/x86_64-linux/openssl-native/1.0.2d-r0/temp/log.do_compile.15132)
> ERROR: Task 1531 (virtual:native:/home/sno/fsl-community-bsp/sources/poky/meta/recipes-connectivity/openssl/openssl_1.0.2d.bb, do_compile) failed with exit code '1'
> 
> Seems I recently used the same session to run my own module tests for a perl module to upload.
> OTOH - it's easy to avoid such a problem by depending on perl-native for openssl(-native).

Whilst you could add this dependency, it would have quite a significant
impact on build time. We rely on there being a working perl on the
native system for autotools so there isn't really a good reason to do
this.

Cheers,

Richard



  reply	other threads:[~2015-10-05  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03 12:51 Should openssl(-native) build-depends on perl-native? Jens Rehsack
2015-10-05  8:12 ` Richard Purdie [this message]
2015-11-09  1:42   ` Randy MacLeod
2015-11-09 12:17     ` Burton, Ross
2015-11-11 16:27       ` Jens Rehsack

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=1444032741.5118.5.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rehsack@gmail.com \
    /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