Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/imagemagick: utilities now need C++ support
Date: Tue, 15 Nov 2022 14:01:03 +0100	[thread overview]
Message-ID: <8735akgynk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221111224011.430289-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni via buildroot's message of "Fri, 11 Nov 2022 23:40:10 +0100")

>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:

 > Since upstream commit
 > https://github.com/ImageMagick/ImageMagick/commit/07f3b487f9860fd4eb9422f1a906d0fe83b6fd1c
 > (which first appeared in version 7.1.0-47), ImageMagick forces the
 > need of a C++ compiler to build its utilities. Despite the request of
 > Bernd Kuhls to revert this change, upstream declined.

 > Since this change is causing build failures in our autobuilders, our
 > only choice is to follow the choice of upstream, and disable building
 > the utilities when C++ support is not available.

 > Fixes:

 >   http://autobuild.buildroot.net/results/4283235d697408cf2e70be5e3769dbe6ebb9ddae/

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed to 2022.08.x and 2022.02.x, thanks.

Is imagemagick without the utilities useful?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-11-15 13:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 22:40 [Buildroot] [PATCH] package/imagemagick: utilities now need C++ support Thomas Petazzoni via buildroot
2022-11-13 14:12 ` Yann E. MORIN
2022-11-15 13:01 ` Peter Korsgaard [this message]
2022-11-15 13:43   ` 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=8735akgynk.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --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