From: Paul Eggert <eggert@cs.ucla.edu>
To: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
Cc: bug-gnulib@gnu.org
Subject: Re: "rpl_fprintf" not found if compiled with options "-ggdb -Og"
Date: Sat, 31 Jul 2021 01:31:55 -0700 [thread overview]
Message-ID: <cafbd7a8-e5eb-f3e5-8b69-c0604de4ca22@cs.ucla.edu> (raw)
In-Reply-To: <20210731014311.GA552841@rhi.hi.is>
On 7/30/21 6:43 PM, Bjarni Ingi Gislason wrote:
> Actually I am using the current repository of both "groff" and
> "gnulib".
I can't reproduce the problem that way, either. I'm using Ubuntu 21.04.
I clone Savannah's latest groff
(7ae6d67b7c310c54bb7176c761b1f9719e64201a), run this:
./bootstrap --gnulib-srcdir=$HOME/src/gnu/gnulib-savannah
./configure
make CFLAGS='-ggdb -Og'
and it builds (there are quite a few warnings, which should get fixed,
but nothing fatal to the build). $HOME/src/gnu/gnulib-savannah contains
a copy of Savannah's latest Gnulib (commit
804ac808a9b17d7ee7cf49f7c713c4a4e4d6423f).
The symptoms you're reporting are that of a partial build that isn't
being resumed correctly somehow.
By the way, I've not had much luck with -Og. I have better luck with -O0
when debugging. But then, I mostly debug C code, not C++.
next prev parent reply other threads:[~2021-07-31 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 20:42 "rpl_fprintf" not found if compiled with options "-ggdb -Og" Bjarni Ingi Gislason
2021-07-28 21:37 ` Paul Eggert
2021-07-31 1:43 ` Bjarni Ingi Gislason
2021-07-31 8:31 ` Paul Eggert [this message]
2021-08-01 1:33 ` Bjarni Ingi Gislason
2021-08-01 2:11 ` Paul Eggert
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cafbd7a8-e5eb-f3e5-8b69-c0604de4ca22@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bjarniig@rhi.hi.is \
--cc=bug-gnulib@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).