From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 39576@debbugs.gnu.org
Subject: [bug#39576] qdbm: fix segfault during test
Date: Wed, 12 Feb 2020 18:52:20 +0100 [thread overview]
Message-ID: <877e0rg0c5.fsf@nckx> (raw)
In-Reply-To: <20200212.161457.1945473684782544947.post@thomasdanckaert.be>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
Thomas,
Thomas Danckaert 写道:
> at some point, the package qdbm started running into a segfault
> during the test suite. This small patch fixes that.
>
> If it's ok, I can push the commit myself (I believe I still have
> commit rights), but since I haven't contributed in 2 years, I
> wanted
> to check if the patch meets all the requirements...
Glad to hear you're still a Guixer.
You're listed as ‘inactive’[0], but TBH I don't know what that
means. If you're unable to push and/or interested in reactivating
your account, let us know.
> - `( #:configure-flags (list (string-append
> "LDFLAGS=-Wl,-rpath="
> - (assoc-ref
> %outputs "out")
> - "/lib"))))
> + `(#:configure-flags (list (string-append
> "LDFLAGS=-Wl,-rpath="
> + (assoc-ref
> %outputs "out")
> + "/lib"))
I'd add a short ‘Fix a segmentation fault in the test suite’
comment here.
> + #:make-flags '("CFLAGS=-fPIC")))
Sticking to one idiom (list …) is slightly newbie-friendlier, but
LGTM either way.
Thanks!
T G-R
[0]: https://savannah.gnu.org/project/memberlist.php?group=guix
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-02-12 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 15:14 [bug#39576] qdbm: fix segfault during test Thomas Danckaert
2020-02-12 17:52 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-02-22 16:49 ` bug#39576: qdbm Thomas Danckaert
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e0rg0c5.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=39576@debbugs.gnu.org \
--cc=me@tobias.gr \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).