From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 484D9C433F5 for ; Fri, 1 Apr 2022 11:42:05 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id F3D49844B2; Fri, 1 Apr 2022 11:42:04 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pHHM7G1fz5Rk; Fri, 1 Apr 2022 11:42:04 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp1.osuosl.org (Postfix) with ESMTP id C2A678448A; Fri, 1 Apr 2022 11:42:02 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by ash.osuosl.org (Postfix) with ESMTP id 7BEF11BF355 for ; Fri, 1 Apr 2022 11:42:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 69A8840538 for ; Fri, 1 Apr 2022 11:42:01 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWb8olSsc_G2 for ; Fri, 1 Apr 2022 11:42:00 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) by smtp2.osuosl.org (Postfix) with ESMTPS id 59355403C4 for ; Fri, 1 Apr 2022 11:42:00 +0000 (UTC) Received: by mail-io1-xd2d.google.com with SMTP id z6so2909937iot.0 for ; Fri, 01 Apr 2022 04:42:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TDI1zhRU6idrywD/ryu/UzKKjh8IyjwH0XvkPeEIRN8=; b=BRJifLadO135VU+SA2DboW/7pcZAjhJTVtiREqpaFTuegDKoQGBnkpBpIVarTvZGs8 q30W1aOVmk+mhEimFVmejjvWKz/I6HJQCn2yGoLMUZ07FDVsAmqrSNvMpXBTLDAlENUv Vmay97+6nEQML28QMcKOzpl1VpRRWAT7bi8BuAuBP0fgwsyMdWt/P4oO2XCJRyGEY5Uk Nil+Dh53F4bav7ejBka0amuZAwbh8KL0+aiy/0HOlBgTdc3Y5MaovMt2T/Mj9d9QOWN9 +FBNU/XGOmrFFoqyTArr3glLShEIUk2JCjXBe0/kF3n3bOX/Fom5z3CoJnaCnZ482jFy 3Lag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TDI1zhRU6idrywD/ryu/UzKKjh8IyjwH0XvkPeEIRN8=; b=q5eOcUBfl/bxtAb2QI099c7LFqlPA80dRm8kE6MepuTpBmEil0BzqSmuRtPa9BkGe2 EGmmP3TIKrdO5eYB8NO0I7MPVsD5AHOAkFbYxdMWcjlXimHf0bi9eDrNUfxt367JQyxW 6StMYYlCjS16evKaUJsqeH0w+dz3ITej4QerT98WGLIZTrbaNQIH3nLBRdmCB1v80DWj ZvATByi5ZlaHc+jzL3SKCg/MBojAKvZvtGASoBq1sJ8V9dCO/c+XgREzziFQL0M6ZIY5 EJSEF4t0H7uJdRrfCelhSfepGACMIH0V24Y4KR/Yt7ns+uUWYX03UwpzXw2z1O4G9XRl +2Tg== X-Gm-Message-State: AOAM5307rG88xuspzgWB++RHEVwnq9gRRrajDhU2icPdZdDaaGE3WcC6 0PCVpWeAzz1MdZYz0TNbB/I7DgccKfX367QBPSrb8vT8H44= X-Google-Smtp-Source: ABdhPJw590ca5zfd198CgrYOdRyVctozSd1MUBsBtso8ocZ69ukeBXo30A7ZkvE2UwulgZ7pIb/YxjvnPKuaHckzKVw= X-Received: by 2002:a05:6638:2601:b0:31a:632e:3d69 with SMTP id m1-20020a056638260100b0031a632e3d69mr5507954jat.229.1648813319429; Fri, 01 Apr 2022 04:41:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sourabh Hegde Date: Fri, 1 Apr 2022 13:41:48 +0200 Message-ID: To: Quentin Schulz Subject: Re: [Buildroot] Buildroot | ninja build error | /usr/bin/ld:error adding symbols: file in wrong format X-BeenThere: buildroot@buildroot.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: buildroot@buildroot.org Content-Type: multipart/mixed; boundary="===============3249352768210680966==" Errors-To: buildroot-bounces@buildroot.org Sender: "buildroot" --===============3249352768210680966== Content-Type: multipart/alternative; boundary="00000000000034a24805db9644e0" --00000000000034a24805db9644e0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Quentin, make casync > > if you want it in an image created by Buildroot, modify your config with > make menuconfig and save your changes, then run make. > But will this create binary for host system also? Sorry, its bit confusing here. I need casync tool use with "rauc" as given in https://rauc.readthedocs.io/en/latest/advanced.html#creating-casync-bundles When I do "rauc convert --cert=3D --key=3D --keyring=3D conventional-bundle.raucb casync-bundle.raucb" I get: "Failed to create bundle: Failed to start casync: Failed to execute child process ?casync? (No such file or directory)" So, casync doesn't exist. My understanding is that Buildroot should be able to properly set up meson for cross-compilation. I ran make casync and now casync is part of rootfs image. But I need casync on host to use with rauc. Any advice on how to proceed will be helpful. Thanks in advance On Fri, 1 Apr 2022 at 11:50, Quentin Schulz < quentin.schulz@theobroma-systems.com> wrote: > Hi, > > On 4/1/22 11:42, Sourabh Hegde wrote: > > Hello Quentin, > > > > Thanks for the update. > > > > I am following this guideline > > > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_systemd= _casync-23building-2Dcasync&d=3DDwIFaQ&c=3D_sEr5x9kUWhuk4_nFwjJtA&r=3DLYjLe= xDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=3DE7Vx6coYDXR= Y655Egik49UZpZDdQ2JWKiYWJBrFF9kw3yPPVRGS-GvW7LrRZTcZV&s=3DRs7PUiLj89kkH7rFu= 4ocmrVT20cGAtkh-dF1BLw4Dns&e=3D > . It says to build casync > > run: > > > > meson build && ninja -C build && sudo ninja -C build install > > > > Actually, meson-build is successful but while running "ninja -C build" = I > am > > getting above errors. > > > > Upstream projects usually don't account for cross-compilation and some > tricks might be needed for build systems to correctly compile some > pieces of software. So just reuse whatever the build system is giving > you first before trying without. That means using package > makefiles/recipes if they already exist. > > > Having the actual package makefile for your casync package would help a > >> lot if it still does not work. > >> > > > > I found this in > > > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__github.com_buildro= ot_buildroot_blob_master_package_casync_casync.mk&d=3DDwIFaQ&c=3D_sEr5x9kUW= huk4_nFwjJtA&r=3DLYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-17= 2IIy1t&m=3DE7Vx6coYDXRY655Egik49UZpZDdQ2JWKiYWJBrFF9kw3yPPVRGS-GvW7LrRZTcZV= &s=3DqykqjQKn5qe2ldZRFFEFO8SkK7wArzNb80WRnjwPc3s&e=3D > > > > But how to use this to compile casync? > > > > make casync > > if you want it in an image created by Buildroot, modify your config with > make menuconfig and save your changes, then run make. > > Cheers, > Quentin > --00000000000034a24805db9644e0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello=C2=A0Quentin,

make casync

if you want it in an image cre= ated by Buildroot, modify your config with
make menuconfig and save your= changes, then run make.

But will this = create binary for host system also? Sorry, its bit confusing here.

I need casync tool use with "rauc" as given in= =C2=A0https://rauc.readthedocs.io/en/latest/advanced.html#crea= ting-casync-bundles=C2=A0

When I do "rauc= convert=C2=A0--cert=3D<certfile> --key=3D<keyfile> --keyring= =3D<keyring> conventional-bundle.raucb casync-bundle.raucb"

I get:

"Failed to create= bundle: Failed to start casync: Failed to execute child process ?casync? (= No such file or directory)"

So, casync do= esn't exist.

My understanding is that Buildroo= t should be able to properly set up meson for cross-compilation.=C2=A0

I ran make casync and now casync=C2=A0is part of rootf= s image. But I need casync on host to use with rauc.

Any advice on how to proceed will be helpful.

T= hanks in advance

On Fri, 1 Apr 2022 at 11:50, Quentin Schulz <quentin.schulz@theobroma= -systems.com> wrote:
Hi,

On 4/1/22 11:42, Sourabh Hegde wrote:
> Hello Quentin,
>
> Thanks for the update.
>
> I am following this guideline
> https://urldefense.proofpoint.com/v2/url?= u=3Dhttps-3A__github.com_systemd_casync-23building-2Dcasync&d=3DDwIFaQ&= amp;c=3D_sEr5x9kUWhuk4_nFwjJtA&r=3DLYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP= 6m6qZZ4njZguQhZhkI_-172IIy1t&m=3DE7Vx6coYDXRY655Egik49UZpZDdQ2JWKiYWJBr= FF9kw3yPPVRGS-GvW7LrRZTcZV&s=3DRs7PUiLj89kkH7rFu4ocmrVT20cGAtkh-dF1BLw4= Dns&e=3D=C2=A0 . It says to build casync
> run:
>
> meson build && ninja -C build && sudo ninja -C build i= nstall
>
> Actually, meson-build is successful but while running "ninja -C b= uild" I am
> getting above errors.
>

Upstream projects usually don't account for cross-compilation and some =
tricks might be needed for build systems to correctly compile some
pieces of software. So just reuse whatever the build system is giving
you first before trying without. That means using package
makefiles/recipes if they already exist.

> Having the actual package makefile for your casync package would help = a
>> lot if it still does not work.
>>
>
> I found this in
> https://urldefense.p= roofpoint.com/v2/url?u=3Dhttps-3A__github.com_buildroot_buildroot_blob_mast= er_package_casync_casync.mk&d=3DDwIFaQ&c=3D_sEr5x9kUWhuk4_nFwjJtA&a= mp;r=3DLYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&= ;m=3DE7Vx6coYDXRY655Egik49UZpZDdQ2JWKiYWJBrFF9kw3yPPVRGS-GvW7LrRZTcZV&s= =3DqykqjQKn5qe2ldZRFFEFO8SkK7wArzNb80WRnjwPc3s&e=3D
>
> But how to use this to compile casync?
>

make casync

if you want it in an image created by Buildroot, modify your config with make menuconfig and save your changes, then run make.

Cheers,
Quentin
--00000000000034a24805db9644e0-- --===============3249352768210680966== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot --===============3249352768210680966==--