From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 97D66E009AC; Fri, 23 Sep 2016 05:20:09 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (oliver.graute[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [74.125.82.66 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mail-wm0-f66.google.com (mail-wm0-f66.google.com [74.125.82.66]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 2AFDBE007B7 for ; Fri, 23 Sep 2016 05:20:05 -0700 (PDT) Received: by mail-wm0-f66.google.com with SMTP id w84so2534258wmg.0 for ; Fri, 23 Sep 2016 05:20:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=rDrVqYw7TuOnNGASfvHQGik8fcWp+qtM9XGJoqi9KEc=; b=I1ik6Ml92zVfe2Phau6QWlAnhjLc9NbdDrBajF0B/ieSOKYCrFH/5VvqHGRZD92bYV 5uayBOfg/eALghfCpnYZ9Lkq7SrXhXZ3sD5wa0VKJMlGq3ObZlynbvzDsZTusVxsxdF0 1aot1RpFxrOc5f4gD9irlk/QtsnnQXtM+KQhT7QZtBKXXS4ZVAlNmoU/BF8XTQZc+rmU 5VQc4KbhvI0AhoVQtUUw0bqJ0Bh7MCjYcFK67/jhK40zT02aPcVhqLnFDXc0R04ULQv0 F033KEAhwDZ5O40LuIfZ3gaWW2NDIbLXMnBjDq+B5JlixMGu2x6G5TlB+AXEqVluAMuH Wy7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=rDrVqYw7TuOnNGASfvHQGik8fcWp+qtM9XGJoqi9KEc=; b=I2g30MqrDmioWsKpA3ijMS+M8rpI30aYzWK0ErOoaoeCtb3OeoHI2zz7MjuOCBNYBk D1vs9nEKCS1Oa8FmreEFIqbfOxu2Cnc+I0S54vKYRLCBNIQ9znHdBkNVkWoPXiAeJ4cT B88tc69/fc3b7Fsnz+ZtYK7XkHW4OrvqhVy8jjUCoPh3jeXwLkharyBemRNHa6xIQegj SY8c6TFYLIoIDzYV3FkzaB9n33C+57dSYM6jUEvbtG5d4Cl2YRJNMl+Kh8Vsbabiatyn ipoSvUnmcjSDU7zvk2BlMrX2QRXUZuzYFw6lo70tCGjYeby5faNdD4hTimPmrnb+gSqT UPpA== X-Gm-Message-State: AA6/9Rl/6FJwODDW/aoAzxqY6wg5AvodJWA1O6SBvPQSLosgeuiMcZleNvbbEywOkgqnCQ== X-Received: by 10.28.21.193 with SMTP id 184mr2730979wmv.26.1474633204572; Fri, 23 Sep 2016 05:20:04 -0700 (PDT) Received: from localhost (x4e3608fd.dyn.telefonica.de. [78.54.8.253]) by smtp.gmail.com with ESMTPSA id bc5sm6951555wjb.37.2016.09.23.05.20.03 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 23 Sep 2016 05:20:03 -0700 (PDT) Date: Fri, 23 Sep 2016 14:19:20 +0200 From: Oliver Graute To: yocto@yoctoproject.org Message-ID: <20160923121920.GA13394@graute-opti> Mail-Followup-To: yocto@yoctoproject.org References: <20160916082406.GB27958@graute-opti> <20160919115820.GC27958@graute-opti> <20160922071643.GE27958@graute-opti> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: build ntp with openssl support X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2016 12:20:09 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 22/09/16, Khem Raj wrote: > On Thu, Sep 22, 2016 at 12:16 AM, Oliver Graute wrote: > > On 19/09/16, Oliver Graute wrote: > >> On 16/09/16, Andre McCurdy wrote: > >> > On Fri, Sep 16, 2016 at 1:24 AM, Oliver Graute wrote: > >> > > Hello, > >> > > > >> > > how can I build ntp with openssl support? > >> > > > >> > > I already created a ntp_%.bbappend file to extend the recipe ntp_4.2.8p4.bb. > >> > > > >> > > FILESEXTRAPATHS_prepend := "${THISDIR}/files:" > >> > > >> > You don't really need this line unless you are adding a file to > >> > SRC_URI or replacing a file already in SRC_URI with your own version. > >> > > >> > > PACKAGECONFIG += "openssl" > >> > > >> > This will enable openssl, but it will also disable all the default > >> > PACKAGECONFIG options (cap, debug and refclocks) which is probably not > >> > what you want. Try this instead: > >> > > >> > PACKAGECONFIG_append = " openssl" > >> > > >> > Note the space between " and openssl. It's required. > >> > >> ok now I see the right configure script options during the configuration > >> of the ntp build. > >> > >> --with-openssl-libdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib > >> --with-openssl-incdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include > >> --with-crypto > >> > >> But ntp is still build without openssl support. The configure scripts > >> can't find the relevant openssl stuff. > >> > >> configure:34762: checking for openssl library directory > >> configure:34802: result: no > >> configure:34807: WARNING: libcrypto and libssl not found in any of /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib > >> configure:34811: checking for openssl include directory > >> configure:34833: result: /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include > >> configure:34877: checking if we will use crypto > >> configure:34879: result: no > >> configure:35109: checking if we want to use OpenSSL's crypto random (if available) > >> configure:35119: result: yes > >> > >> some clue whats wrong here? > > > > in my sysroots/imx6ulevk/usr/lib I have > > > > ls -la libssl* > > > > libssl3.so > > libssl.a > > libssl.so -> libssl.so.1.0.0 > > libssl.so.1.0.0 > > > > ls -la libcrypt* > > > > libcrypt.a > > libcrypt_pic.a > > libcrypt_pic.map > > libcrypt.so -> ../../lib/libcrypt.so.1 > > > > > > but no libcrypto.so. I guess thats the reason why my ntp configure > > script is complaining. > > > > Some ideas how to get libcrypto.so in my /usr/lib folder in the yocto > > sysroot? > > > > It seems your openssl is not being compiled correctly. Can you go into > builddir or openssl > and see if libcrypto.so.1.0.0 is built ? if not then you have to do > some digging why its not > configuring to build libcrypto libcrypto is build by openssl openssl/1.0.2d-r0/openssl-1.0.2d$ ls -la libcrypt* libcrypto.a libcrypto.pc libcrypto.so -> libcrypto.so.1.0.0 libcrypto.so.1.0.0 but in my sysroot libcrypto is located in lib NOT in usr/lib the ntp recipe in meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p4.bb defines: --with-openssl-libdir=${STAGING_LIBDIR} I assume I need ${STAGING_BASELIBDIR} here instead. But currently I fail with overwriting this in my bbappend file. If I use EXTRA_OECONF to overwrite it in my bbappend I see two --with-openssl-libdir statements while configuring. The first with /lib the second one with /usr/lib. EXTRA_OECONF += "\ --with-openssl \ --with-openssl-libdir=${STAGING_BASELIBDIR} \ --with-openssl-incdir=${STAGING_INCDIR} \ --with-crypto \ " Best Regards, Oliver