From: Georg Rudoy <0xd34df00d@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] ghc support in multilib-build.eclass
Date: Wed, 9 Aug 2023 18:42:25 -0500 [thread overview]
Message-ID: <CAGbUWSJfdhneYxJWxAYii43vanR-qjnWzOnCqZsng5P2meWRbQ@mail.gmail.com> (raw)
Hi,
Right now, the configuration header generated for packages like
openssl by multilib-build.eclass doesn't play nicely with ghc.
Long story short, ghc runs `gcc -E` with `-undef`, which causes the
`#if defined(__x86_64__)` branch (or whatever is the relevant one) to
be missed, falling back to
```
error "No ABI matched, please report a bug to bugs.gentoo.org"
```
There is already a workaround for Swig in the template.
I propose extending this workaround with a very small change, replacing
```
#elif defined(SWIG)
```
with
```
#elif defined(SWIG) || defined(__GLASGOW_HASKELL__)
```
in the template inside the eclass.
If everybody's happy with that, I'll be also happy to open a PR with
that change.
--
Georg Rudoy
next reply other threads:[~2023-08-09 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 23:42 Georg Rudoy [this message]
2023-08-10 1:54 ` [gentoo-dev] ghc support in multilib-build.eclass Michał Górny
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=CAGbUWSJfdhneYxJWxAYii43vanR-qjnWzOnCqZsng5P2meWRbQ@mail.gmail.com \
--to=0xd34df00d@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/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