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: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Libarchive always throws an error when building
Date: Wed, 1 Feb 2023 19:04:50 +0100	[thread overview]
Message-ID: <20230201190450.4636771a@gmx.net> (raw)
In-Reply-To: <20230201184154.2c7e2680@gmx.net>

Hello *,

On Wed, 1 Feb 2023 18:41:54 +0100, Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Roland,
> 
> On Wed, 1 Feb 2023 15:57:52 +0000, Kenneth Roland <kjroland75@hotmail.com> wrote:
> 
> > Hello Buildroot team,
> > I guess this is my way of submitting a bug report, here goes.
> > 
> > Current .config is attached, but renamed as buildroot.config as I couldn't get Dolphin (KDE) to show the hidden file. This project of mine was to build an ISO for an old Thinkpad that would act as a reciever from https://github.com/badaix/snapcast, but I couldn't find anything useful on this libarchive error. "libarchive-dev" is installed on the host using "apt install". You guys probably know how to recreate this, but the host is just a Debian netinst, no DE, and then git installed. Installed dependencies as of https://medium.com/@hungryspider/building-custom-linux-for-raspberry-pi-using-buildroot-f81efc7aa817, cloned the Buildroot repo from Github, " make pc_x86_64_bios_defconfig", and then replaced the .config file generated by the one I used the first time (was sanity/dependancy checking). Ran make, which ran for about a good 30-45 mins until it stopped and I saw the libarchive error.
> > 
> > Host info (uname -a)
> > Linux blackbox 6.0.0-0.deb11.6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1~bpo11+1 (2022-12-19) x86_64 GNU/Linux
> > 
> > ```checking whether the /mnt/hdd/buildroot/output/host/bin/x86_64-buildroot-linux-gnu-gcc linker (/mnt/hdd/buildroot/output/host/bin/x86_64-buildroot-linux-gnu-ld -m elf_
> > x86_64) 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... yes
> > checking for LIBARCHIVE... no
> > configure: error: Package requirements (libarchive) were not met:
> > 
> > Package 'iconv', required by 'libarchive', not found
> > 
> > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > installed software in a non-standard prefix.
> > 
> > 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.
> > make: *** [package/pkg-generic.mk:283: /mnt/hdd/buildroot/output/build/opkg-0.4.5/.stamp_configured] Error 1```  
> 
> From host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/pkgconfig/libarchive.pc:
> 
> 	[...]
> 	Requires.private: iconv libssl libcrypto
> 
> 
> From build/libarchive-3.6.2/configure.ac:
> 
> 	AC_ARG_WITH([iconv],
> 	  AS_HELP_STRING([--without-iconv], [Don't try to link against iconv]))
> 
> 
> And with the following local buildroot patch:
> 
> diff --git a/package/libarchive/libarchive.mk b/package/libarchive/libarchive.mk
> index cfc148d01d..02cca9cee9 100644
> --- a/package/libarchive/libarchive.mk
> +++ b/package/libarchive/libarchive.mk
> @@ -70,7 +70,7 @@ endif
>  ifeq ($(BR2_PACKAGE_LIBICONV),y)
>  LIBARCHIVE_DEPENDENCIES += libiconv
>  else
> -LIBARCHIVE_CONF_OPTS += --without-libiconv-prefix
> +LIBARCHIVE_CONF_OPTS += --without-libiconv-prefix --without-iconv
>  endif

But the right fix should be this [1] libarchive upstream commit (untested)...

Regards,
Peter


[1] https://github.com/libarchive/libarchive/commit/1f35c466aaa9444335a1b854b0b7223b0d2346c2


>  
>  ifeq ($(BR2_PACKAGE_LIBXML2),y)
> 
> 
> The opkg package builds without errors (after re-build of the libarchive package)...
> 
> Regards,
> Peter
> 
> 
> > 
> > [https://miro.medium.com/max/1200/0*6J1fXBTEsPODw5I5]<https://medium.com/@hungryspider/building-custom-linux-for-raspberry-pi-using-buildroot-f81efc7aa817>
> > Building custom Linux for Raspberry Pi using Buildroot<https://medium.com/@hungryspider/building-custom-linux-for-raspberry-pi-using-buildroot-f81efc7aa817>
> > Connect the USB end of the USB to Serial cable to your computer and open the serial port using a serial terminal software such as Gtkterm with baud rate set to 115200 .
> > medium.com
> > 
> > 
> > 
> > 
> > 
> > [https://opengraph.githubassets.com/39abea8770e3ae33931f8598335f8b3b04f8a288fcc7e7f4579cf2ea74afbb37/badaix/snapcast]<https://github.com/badaix/snapcast>
> > GitHub - badaix/snapcast: Synchronous multiroom audio player<https://github.com/badaix/snapcast>
> > Installation from source. Please follow this guide to build Snapcast for. Linux; FreeBSD; macOS; Android; OpenWrt; Buildroot; Raspberry Pi; Windows; SnapOS. The bravest among you may be interested in SnapOS, a small and fast-booting "just enough" OS to run Snapcast as an appliance.. There is a guide (with the necessary buildfiles) available to build SnapOS, which comes in two flavors:
> > github.com
> > 
> > 
> > 
> > 
> > 
> >   
> 

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

  reply	other threads:[~2023-02-01 18:05 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 [this message]
2023-02-01 19:27       ` Kenneth Roland
2023-02-02 20:41         ` Peter Seiderer

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=20230201190450.4636771a@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@buildroot.org \
    --cc=kjroland75@hotmail.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