Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Jesse Van Gavere <jesseevg@gmail.com>,
	 Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 2/5] package/stellarium: add extra downloads
Date: Sat, 30 May 2026 22:36:59 +0200	[thread overview]
Message-ID: <ahtKVlY-bPFhqTg7@windsurf> (raw)
In-Reply-To: <20260530155718.657095-2-bernd@kuhls.net>

Hello,

On Sat, May 30, 2026 at 05:57:15PM +0200, Bernd Kuhls wrote:
> Building Stellarium includes the download of external tarballs during
> configure.
> 
> This fails with host-cmake during configure stage:
> 
> CMake Error at md4c-subbuild/md4c-populate-prefix/src/md4c-populate-stamp/download-md4c-populate.cmake:163 (message):
>   Each download failed!
> 
>     error: downloading 'https://github.com/mity/md4c/archive/refs/tags/release-0.5.2.tar.gz' failed
>           status_code: 1
>           status_string: "Unsupported protocol"
>           log:
>           --- LOG BEGIN ---
>           Protocol "https" not supported
> 
>   closing connection #-1
> 
> due to buildroot commit f87138339b17bc2b1d84c59ea176abb941413550 which
> disabled SSL support for host-cmake.
> 
> This patch uses _EXTRA_DOWNLOADS to provide these tarball to allow
> offline builds.
> 
> No autobuilder error was recorded, the build error can be reproduced
> with this defconfig:
> 
> BR2_x86_64=y
> BR2_x86_corei7=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_X86_64_CORE_I7_GLIBC_BLEEDING_EDGE=y
> BR2_FORCE_HOST_BUILD=y
> BR2_PACKAGE_STELLARIUM=y
> BR2_PACKAGE_MESA3D=y
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SOFTPIPE=y
> BR2_PACKAGE_MESA3D_OPENGL_GLX=y
> BR2_PACKAGE_QT5=y
> BR2_PACKAGE_XORG7=y
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to master, thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-05-30 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 15:57 [Buildroot] [PATCH v2 1/5] package/stellarium: fix qt5serialport dependency Bernd Kuhls
2026-05-30 15:57 ` [Buildroot] [PATCH v2 2/5] package/stellarium: add extra downloads Bernd Kuhls
2026-05-30 20:36   ` Thomas Petazzoni via buildroot [this message]
2026-06-05 12:49   ` Thomas Perale via buildroot
2026-05-30 15:57 ` [Buildroot] [PATCH v2 3/5] package/stellarium: bump version to 26.1 Bernd Kuhls
2026-05-30 20:46   ` Thomas Petazzoni via buildroot
2026-05-30 15:57 ` [Buildroot] [PATCH v2 4/5] package/qt6/qt6positioning: new package Bernd Kuhls
2026-05-30 21:15   ` Thomas Petazzoni via buildroot
2026-05-30 15:57 ` [Buildroot] [PATCH v2 5/5] package/stellarium: allow build with qt6 Bernd Kuhls
2026-05-30 21:20   ` Thomas Petazzoni via buildroot
2026-05-30 20:33 ` [Buildroot] [PATCH v2 1/5] package/stellarium: fix qt5serialport dependency Thomas Petazzoni via buildroot

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=ahtKVlY-bPFhqTg7@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=jesseevg@gmail.com \
    --cc=roykollensvendsen@gmail.com \
    --cc=thomas.petazzoni@bootlin.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