Presumably you've a recipe for the vendor openssl. If it has the same
name but is a different version then just set PREFERRED_VERSION. If
it has a different name too, it should PROVIDE openssl and you can
just set PREFERRED_PROVIDER.
If it doesn't do either of those things, then it is broken.
R
The easiest thing would be to edit the installer script that goes into
the hddimg to create your extra partitions and whatever else you want
done.
Ross
On 6 July 2018 at 22:52, Raymond Yeung wrote:
> Is there any installer that I could download along with the .hddimg (or
> .iso) image to the RAM
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
I tried poky/scripts/contrib/mkefidisk.sh. It showed promised as 3 primary
partitions are created on my SSD instead of just 1 when I used dd to write
.hddimg. However, I ran into a number of failures when I ran this script:
1. mktemp fails, as the .sh uses 3 "X" instead of 6 "X" as temporary
Tim Hammer wrote:
> Can anyone point me to a step-by-step tutorial or simple how-to on
> creating and using an initramfs with my kernel for ARM aarch64?
>
>
> I have tried creating my own:
> - boot-image.bb file with IMAGE_FSTYPES = "cpio.gz".
> - local.conf has INITRAMFS_IMAGE_BUNDLE = "1"
>
On Sat, Jul 7, 2018 at 12:37 PM, Tim Hammer wrote:
>
>
> On Fri, Jul 6, 2018 at 6:02 PM, Andre McCurdy wrote:
>
>> On Fri, Jul 6, 2018 at 1:22 PM, Tim Hammer wrote:
>> >
>> > Thanks for the responses to my first email. I was able to get a working
>> > initramfs in my kernel image that allowed m
On Fri, Jul 6, 2018 at 6:02 PM, Andre McCurdy wrote:
> On Fri, Jul 6, 2018 at 1:22 PM, Tim Hammer wrote:
> >
> > Thanks for the responses to my first email. I was able to get a working
> > initramfs in my kernel image that allowed me to do the initial
> evaluation of
> > my solution.
>
> What wa
Signed-off-by: Armin Kuster
---
.../nmap-redefine-the-python-library-dir.patch | 37 ---
...shtool-mkdir-with-coreutils-mkdir-command.patch | 48 ---
recipes-security/nmap/nmap_7.60.bb | 54 --
3 files changed, 139 deletions(-)
I do not recommend that you copy the binary over; it's better to clearly
separate native and target. Just patch the makefile.
Alex
2018-07-07 13:30 GMT+02:00 Timm :
> Am 07.07.2018 um 12:17 schrieb Alexander Kanavin:
>
> How to do this is specific to each project. Generally, you want the
> targe
Am 07.07.2018 um 12:17 schrieb Alexander Kanavin:
> How to do this is specific to each project. Generally, you want the
> target recipe to depend on the native recipe (so that the necessary
> native tools show up in the target sysroot),
Done that: gutenprint depends on gutenprint-native.
> and the
How to do this is specific to each project. Generally, you want the
target recipe to depend on the native recipe (so that the necessary
native tools show up in the target sysroot), and then you need to
study the build system of the upstream component project (makefiles
etc.) to see how it can be in
There was a gutenprint recipe back in OE-Classic:
https://layers.openembedded.org/layerindex/oe-classic/recipe/12076/
But currently there is no gutenprint available for Yocto.
I tried to build my own recipe. But I got stuck at the stage where the
build process wants to call some generated binarie
12 matches
Mail list logo
