From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Jami bug source investigation #4
Date: Mon, 6 Jul 2020 02:30:31 +0200 [thread overview]
Message-ID: <20200706023031.19b766e6@interia.pl> (raw)
In-Reply-To: <877dvh3dua.fsf@cbaines.net>
Hi,
On Sun, 05 Jul 2020 21:29:33 +0100
Christopher Baines <mail@cbaines.net> wrote:
>
> So, I tried adding -DNDEBUG to the CFLAGS bit of the
> #:configure-flags, and the package built. Testing it out seems to
> work, I think I've experienced this issue with assertion failures, so
> hopefully this will help.
>
> modified gnu/packages/jami.scm
> @@ -141,7 +141,7 @@
> ;; against pjproject-jami:
> ;; relocation R_X86_64_32S against `.rodata' can not
> be used when ;; making a shared object;
> - "CFLAGS=-fPIC"
> + "CFLAGS=-fPIC -DNDEBUG"
> "CXXFLAGS=-fPIC")
> #:phases
> (modify-phases %standard-phases
>
> Is there more to applying this fix, or will this change alone help?
> I'm more than happy to review patches.
>
> Thanks,
>
> Chris
That's it for the bug, if you want to have it fixed quickly, feel free
to commit it. I didn't do it yet, because I'm busy writting commit
messages for my refactored and updated package definitions.
I'm also trying to catch up with the latest Jami version - they fixed
some annoying stuff too.
Is there a script for automatically writing commit messages compliant
with the GNU coding standards?
Jan Wielkiewicz
next prev parent reply other threads:[~2020-07-06 0:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 0:35 Jami bug source investigation #4 Jan Wielkiewicz
2020-06-18 6:52 ` Pierre Neidhardt
2020-06-18 18:22 ` Jan
2020-06-19 23:21 ` Jan Wielkiewicz
2020-06-21 0:38 ` Jan Wielkiewicz
2020-06-22 7:32 ` Pierre Neidhardt
2020-06-22 12:23 ` Jan Wielkiewicz
2020-06-22 12:37 ` Pierre Neidhardt
2020-07-05 20:29 ` Christopher Baines
2020-07-06 0:30 ` Jan Wielkiewicz [this message]
2020-07-06 1:23 ` Jan Wielkiewicz
2020-07-06 15:52 ` Jan Wielkiewicz
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=20200706023031.19b766e6@interia.pl \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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).