From: itd <itd@net.in.tum.de>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Philip Munksgaard <philip@munksgaard.me>,
54729@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#54729] [PATCH] build: haskell-build-system: Support packages w. multiple libraries
Date: Wed, 21 Dec 2022 13:48:12 +0100 [thread overview]
Message-ID: <87cz8c2a9f.fsf@localhost> (raw)
In-Reply-To: <877d1uifzi.fsf@localhost>
Dear Haskell team,
dear all,
itd <itd@net.in.tum.de> writes:
> thanks for the patch! I applied it, tried it, and ran into some build
> issues. [...]
> Ignorant of the patch provided here, I tried to build newer versions of
> ghc-attoparsec / its dependants and ended up with the attached patch.
> Using this patch, the build succeeds (but I am not sure if the patch's
> approach is sensible). [...]
if possible, I'd appreciate feedback on my previous mail. E.g., does my
attempt in using the originally proposed patch make sense? Any opinions
on my patch?
Thank you.
Regards
itd
next prev parent reply other threads:[~2022-12-21 12:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 15:15 [bug#54729] [PATCH] build: haskell-build-system: Support packages w. multiple libraries Philip Munksgaard
2022-04-06 19:19 ` [bug#54729] [PATCH core-updates v2 1/2] build: haskell-build-system: Remove trailing #t zimoun
2022-04-06 19:19 ` [bug#54729] [PATCH core-updates v2 2/2] build: haskell-build-system: Support multiple libraries zimoun
2022-04-06 19:23 ` [bug#54729] [PATCH] build: haskell-build-system: Support packages w. " zimoun
2022-04-07 6:08 ` Lars-Dominik Braun
2022-04-07 6:49 ` Philip Munksgaard
2022-04-07 8:25 ` Philip Munksgaard
2022-04-07 7:35 ` zimoun
2022-04-13 18:59 ` Philip Munksgaard
2022-04-14 18:21 ` Lars-Dominik Braun
2022-04-15 8:19 ` Philip Munksgaard
2022-09-23 9:42 ` itd
2022-12-21 12:48 ` itd [this message]
2022-12-23 14:03 ` Philip Munksgaard
2023-01-06 11:51 ` Lars-Dominik Braun
2023-01-12 17:30 ` itd
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=87cz8c2a9f.fsf@localhost \
--to=itd@net.in.tum.de \
--cc=54729@debbugs.gnu.org \
--cc=lars@6xq.net \
--cc=philip@munksgaard.me \
--cc=zimon.toutoune@gmail.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.
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.