From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [v3 0/2] openssl: parallel build
Date: Thu, 19 Nov 2015 00:14:48 +0100 [thread overview]
Message-ID: <564D0668.6070003@mind.be> (raw)
In-Reply-To: <CAMQcK5+S=aDv3qtA6vdzeqgqSq6Xd4xUBYjvHQat=pg1Ot72gA@mail.gmail.com>
On 18-11-15 20:41, Ryan Barnett wrote:
> Hi Thomas,
>
> On Wed, Nov 18, 2015 at 6:57 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>>
>> I have the feeling that the parallel build patches for OpenSSL are not
>> working properly. Look at the recent build failures we've got for the
>> openssl and host-openssl builds:
>>
>> http://autobuild.buildroot.org/?reason=openssl-1.0.2d
>> http://autobuild.buildroot.org/?reason=host-openssl-1.0.2d
>>
>> They are pretty much all due to a similar error:
>>
>> ln: failed to create symbolic link 'libssl.so': File exists
>> ln: creating symbolic link `libcrypto.so': File exists
>>
>> I could spot only one that is different:
>>
>> In file included from apps.h:117:0,
>> from req.c:74:
>> ../include/openssl/bio.h:521:34: error: expected ';' before 'BIO_ctrl'
>> # define BIO_set_fp(b,fp,c) BIO_ctrl(b,BIO_C_SET_FILE_PTR,c,(char *)fp)
>>
>> Do you have some ideas?
>
> I agree with you in that it looks like are some issues with the
> parallel build. It appears there is a hard to track down race
> condition due a symbolic being created twice during the build but as
> to way I don't have any clue.
I can see where the problem is, but not what the solution is... The
build-shared target depends on do_crypto and link-shared, which will be executed
in parallel. do_crypto calls link_a.linux_shared -> link_a.gnu which does
SYMLINK_SO; in parallel, link-shared calls symlink.linux_shared which also does
SYMLINK_SO. Before the symlink is created, it is rm'ed, but there is a tiny
chance that the second one is created after the rm has been called. Bam.
Maybe just replace the rm with an ln -sf? Don't know if upstream will like that
though.
Regards,
Arnout
>
>> Does Gentoo has some more patches?
>
> No this is the only patch for openssl 1.0.2d. There also hasn't been
> any updates to this patch other then the one that is currently there.
>
>> Should we revert back to non-parallel build for OpenSSL ?
>
> I guess I will leave that up to either yourself or Peter if you feel
> that it should. I don't have time in the next week or two to
> investigate the problem further so I'm OK with reverting this patch.
>
> Thanks,
> -Ryan
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-18 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 12:06 [Buildroot] [v3 0/2] openssl: parallel build Ryan Barnett
2015-09-16 12:06 ` [Buildroot] [v3 1/2] openssl: use git formatted patches Ryan Barnett
2015-09-16 20:22 ` Thomas Petazzoni
2015-09-16 12:06 ` [Buildroot] [v3 2/2] openssl: enable parallel build and installation Ryan Barnett
2015-09-16 20:22 ` Thomas Petazzoni
2015-11-18 12:57 ` [Buildroot] [v3 0/2] openssl: parallel build Thomas Petazzoni
2015-11-18 19:41 ` Ryan Barnett
2015-11-18 23:14 ` Arnout Vandecappelle [this message]
2015-11-24 16:01 ` Mike Frysinger
2015-11-23 13:05 ` Yann E. MORIN
2015-11-23 16:13 ` Thomas Petazzoni
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=564D0668.6070003@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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