[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #60338] newer gnulib will cause 'undefined reference to "rpl_free"'
From: |
G. Branden Robinson |
Subject: |
[bug #60338] newer gnulib will cause 'undefined reference to "rpl_free"' errors |
Date: |
Fri, 20 Aug 2021 21:55:46 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 |
Update of bug #60338 (project groff):
Severity: 3 - Normal => 1 - Wish
Status: Works For Me => None
Summary: compilation error: undefined reference to "rpl_free"
=> newer gnulib will cause 'undefined reference to "rpl_free"' errors
_______________________________________________________
Follow-up Comment #9:
[comment #8 comment #8:]
> Are you using an old version of "gnulib".
I'm using the one from our git submodule, which is the one for which we claim
support.
> My ChangeLog in groff/gnulib is from 15th August 2021.
Yes, you're using something much newer.
> I update my gnulib repository before I use this bootstrap script:
Then you can't expect it to work if gnulib changes something that breaks
compatibility.
> I also use "-DGNULIB_NAMESPACE=gnulib"
Why? What does this do? Why should groff's build use it?
> I am using "autoconf 2.71" now in my configure.
Yes, this is very new, and groff has not updated its dependencies yet. Doing
so depends on how easy this is to do without breaking support for older host
platforms with older versions of underlying tooling.
> I have already reported bugs after an update of gnulib.
This stuff is good to know, but it's not anything more than a "Wish"-severity
bug until the groff development team decides to update the build dependencies
we support. That's a collective decision that should be made on the mailing
list, and last I checked Bertrand was still our GNU maintainer and release
engineer.
> It is not enough to just update gnulib in master before a release.
That is a question of policy and resource management.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60338>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/