Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Kenneth Roland <kjroland75@hotmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
	Pierre-Jean Texier <texier.pj2@gmail.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Libarchive always throws an error when building
Date: Thu, 2 Feb 2023 21:41:16 +0100	[thread overview]
Message-ID: <20230202214116.2478d971@gmx.net> (raw)
In-Reply-To: <BN0PR10MB535047C6BBE609A96984C22ED6D19@BN0PR10MB5350.namprd10.prod.outlook.com>

Hello Roland,

On Wed, 1 Feb 2023 19:27:35 +0000, Kenneth Roland <kjroland75@hotmail.com> wrote:

> Hello Peter,
> After applying the patch you mentioned<https://github.com/libarchive/libarchive/commit/1f35c466aaa9444335a1b854b0b7223b0d2346c2>, as well as installing libssl-dev, I now have this error.

Host installed packages are ignored by the buildroot system, never do this...

> 
> 
> ​```checking whether the /mnt/hdd/sct/output/host/bin/aarch64-buildroot-linux-gnu-gcc linker (/mnt/hdd/sct/output/host/bin/aarch64-buildroot-linux-gnu-ld) supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking pkg-config is at least version 0.20... /mnt/hdd/sct/output/host/bin/pkgconf: error while loading shared libraries: libpkgconf.so.3: cannot open shared object file: No such file or directory
> no
> checking for LIBARCHIVE... no
> configure: error: in `/mnt/hdd/sct/output/build/opkg-0.4.5':
> configure: error: The pkg-config script could not be found or is too old.  Make sure it
> is in your PATH or set the PKG_CONFIG environment variable to the full
> path to pkg-config.
> 
> Alternatively, you may set the environment variables LIBARCHIVE_CFLAGS
> and LIBARCHIVE_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> 
> To get pkg-config, see <http://pkg-config.freedesktop.org/>.
> See `config.log' for more details
> make: *** [package/pkg-generic.mk:283: /mnt/hdd/sct/output/build/opkg-0.4.5/.stamp_configured] Error 1```

See the proper patch from Bernd Kuhls (including AUTORECONF and host-pkagconf dependency):

	http://lists.busybox.net/pipermail/buildroot/2023-February/660921.html
	https://patchwork.ozlabs.org/project/buildroot/patch/20230201181005.731564-1-bernd.kuhls@t-online.de/

Regards,
Peter

> 
> 
> From a quick search, libpkgconf.so.3 is found on RPM systems, which isn't the case here, but somehow it has something to do with pkg-config being too old. Do I need to update my path, and if so, is that the bash file found in my user's home folder? Or is there another patch I can apply? Thanks,
> Kenneth

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-02-02 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BN0PR10MB535094D28596AC0858222678D6D19@BN0PR10MB5350.namprd10.prod.outlook.com>
2023-02-01 15:57 ` [Buildroot] Libarchive always throws an error when building Kenneth Roland
2023-02-01 17:41   ` Peter Seiderer
2023-02-01 18:04     ` Peter Seiderer
2023-02-01 19:27       ` Kenneth Roland
2023-02-02 20:41         ` Peter Seiderer [this message]

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=20230202214116.2478d971@gmx.net \
    --to=ps.report@gmx.net \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=kjroland75@hotmail.com \
    --cc=texier.pj2@gmail.com \
    /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