From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 271C8E00D63; Sun, 8 Jul 2018 19:05:12 -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=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [216.168.135.166 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from starfish.geekisp.com (starfish.geekisp.com [216.168.135.166]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B0E63E00D63 for ; Sun, 8 Jul 2018 19:05:09 -0700 (PDT) Received: (qmail 10405 invoked by uid 1003); 9 Jul 2018 02:05:08 -0000 Received: from unknown (HELO ?172.19.249.100?) (philip@opensdr.com@38.98.37.142) by mail.geekisp.com with (DHE-RSA-AES128-SHA encrypted) SMTP; 9 Jul 2018 02:04:58 -0000 To: Raymond Yeung , "yocto@yoctoproject.org" References: From: Philip Balister Openpgp: preference=signencrypt Autocrypt: addr=philip@balister.org; prefer-encrypt=mutual; keydata= xsBNBE6PN4EBCADXwOSVOvTrJ370tH2RmiR22OuCBcKfnKTLztyV5zA0veDB1kmrIajh+sJe HWNqsib0v19S3wdrvqzKrztSfNAgUctvkAuTOloU81dmbAjDSge6nFxjzIIz6XjNvmP5xl9J rstPm4i4dhAs5436xf4Bh0vn3C/Bp4fKwXBSW/Xto7vuiuSK03ojon3F8O2WNEmKxHyubFP1 2tNvXOp/PeAR4LTnYq6fdAAofvbpbPDBg8qICe6j1UXaIyU93IbW+bJp1RFbeakWxiTw+eQ2 fVjG5XnubNX0YBlmjHDJhjeqV1uwkImNHlZknecLjT7g37vIMwz+PTfPIhmIGffzqtHlABEB AAHNJVBoaWxpcCBCYWxpc3RlciA8cGhpbGlwQGJhbGlzdGVyLm9yZz7CwH4EEwECACgCGyMG CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJYM1D9BQkRKOdqAAoJEMDJd4rr0merDX4H/3Pr nYKDnml7LRiikoOTFJb4r7ub04skrkGI2DAYvRUPH110KXaan84Qo2Yl4r/ma15Lpqx+cdPR 3KbFlSWyjgY6CMN/BclutsK4mFkoxnmhdYJvc5M2TDfZLxBPMTeQiHo0MwxUB5v81mv812bx YKfEOg3ndk7C/TE0Q8ZER7p6fU3ol/e0ilLyaCpd85nkEcOEI7BdBBGhKWii+Cwvv8g2ofQZ 3wAsqQFp7PFxlEjo5Xc1QGqo7L+UlDG23QjUn33n+wZMZm9EUZFu1c1MAGZsvXiqKw8P07Mj yyf6h6EMVP8wME7gnkxsZkpKv04mSvKpDLIInmRW9ZlHXaJ4YxjOwE0ETo83gQEIAPs+ZC0R gF4blrRIiVHdkARncAxUwSUbti5Ku23dQ0iBizozh4YGucgW48gxsvJCkCc9s/4C9e3vYiCZ GVGC8x6Ll3vE7xwRQ/euVqJ0mXG7tNK1zAPpSgI6aooPSZCW7PBvwY8uMvzzCzP+EBd0+oA5 uXQSEcyOJUYy4beferoHUiBjBkyNd+v2iaJf7KjAYYxJOcPvtnq/VL09hlmtCD5zghOn80rt LqF66BJkHmATopSWyor1qz7gmowdCkFkUJDNW7yJT1wVANqDd9P5A8vYhngwJTHsvXVftmvB gLiJjYuKst36G2AOHgm4ls5jRMa/k7jWue1RKM5LxzgBtLUAEQEAAcLAZQQYAQIADwIbDAUC WDNRbAUJESjn5AAKCRDAyXeK69Jnq1qYB/93aiBdenAuu0H/zGWEFFB14cdhDR4S4q0EbfXl 1z9o3Irazw6WMtLe12zJ4/Xl41Mh/IH8/+AgDnigisrkKRN1TkiOGDUVnS0akkhML3ONbeFd ocYEwBAPDTxAaWNoyjDe/bORokSJn31cFoG6QYyzUct79npHorbaXW0zW+KC77Do53yUKQ8+ icWpfiCMk1YzSHCr0y5NZNVxac9a0+IDzH/YBbNdJLNaMvXcuege1Qqz85pdR0P4XuCVRD2j ZAbcGJzZXlu9ZzpIHjtZoyF8paJRMQwzWEO3/Txksmm7K8eu8Tz2JVpjiOIj44MOTKoRGKjO 6eUfr0u7CwnEyqiQ Message-ID: <81f82708-8e6b-259d-d37d-2a892d9093cf@balister.org> Date: Sun, 8 Jul 2018 19:04:27 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Subject: Re: How to remove openssl from sysroots 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: Mon, 09 Jul 2018 02:05:12 -0000 Content-Type: text/plain; charset=windows-1252 Content-Language: en-MW Content-Transfer-Encoding: 7bit On 07/06/2018 03:06 PM, Raymond Yeung wrote: > I've changed the subject heading to make it more specific to our problem. Hopefully this generates some responses. > > > It has been blocking us for close to one week now. We want to use our 3rd party vendor openssl, not the one that comes with the source. Apparently, even with "minimal" instead of "base" or "sato" cannot exclude it. > > > Any idea [e.g. how do we systematically find out how it's included now, and possibly what other packages/recipes we may also need to remove due to dependency]? I tend to use the ouput of the buildhistory class when I have these questions. Philip > > > Thanks, > > Raymond > > > ________________________________ > From: Raymond Yeung > Sent: Monday, July 2, 2018 11:05 PM > To: yocto@yoctoproject.org > Subject: How to remove a package from a build > > > We've our own non-yocto openssl that we want to use. At the moment, we're using "sato" image, rather than "minimal" and includes its openssl that is out-of-date. What is the best way to exclude it from our image (and from sysroots)? > > > We have thought about two ideas - > > > 1. Use smaller image like core-image-base, or core-image-full-cmdline (but not -minimal that may remove too much functionality). > 2. Use INSTALL_IMAGE_remove += " openssl" > > > Would either one work? Also, how do I follow the .bb files etc (e.g. starting from the one for sato) to trace down which sub-package includes openssl? > > > Thanks, > > Raymond > > >