all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: Arne Babenhauserheide <Arne_Bab@web.de>
Cc: 63572@debbugs.gnu.org
Subject: bug#63572: htmlcxx-0.87 fails to build
Date: Thu, 18 May 2023 18:51:56 +0100	[thread overview]
Message-ID: <fb9dde16-e5b6-55e2-c992-de3d215049f7@makinata.eu> (raw)
In-Reply-To: <trinity-ef0e05ea-e048-4fe0-98d9-45c6dde05639-1684423068739@3c-app-webde-bap11>

Hi Arne,

On 2023-05-18 16:17, Arne Babenhauserheide wrote:
> Hi,
> 
> To reproduce: guix build htmlcxx — it blocks several dependents.
> 
> The relevant part of the error:
> 
> In file included from CharsetConverter.cc:5:
> CharsetConverter.h:20:90: error: ISO C++17 does not allow dynamic exception specifications
>    20 |                         CharsetConverter(const std::string &from, const std::string &to) throw (Exception);
> 
> These were deprecated in C++11 and removed in C++17: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0003r5.html
> 
> So this may just need compiler parameters to set C++11 instead of C++17
> as target.

Looking at the README file from <https://sourceforge.net/p/htmlcxx/code/ci/master/tree/>,
it looks to me that upstream has moved to <https://github.com/bonitao/htmlcxx>. (judging by the name of the repo owner)
Can you try asking upstream for a new release? The last commit (<https://github.com/bonitao/htmlcxx/commit/0ffa3e90b7dc3944f199fd80ab47c2a82589209a>)
has the message 'Fix c+11 compilation'.


Cheers,
Bruno




  reply	other threads:[~2023-05-18 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 15:17 bug#63572: htmlcxx-0.87 fails to build Arne Babenhauserheide
2023-05-18 17:51 ` Bruno Victal [this message]
2023-05-20 21:43   ` bug#63572: [PATCH] " Dr. Arne Babenhauserheide
2023-05-24  8:43     ` Efraim Flashner

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=fb9dde16-e5b6-55e2-c992-de3d215049f7@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=63572@debbugs.gnu.org \
    --cc=Arne_Bab@web.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.