bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #66438] configure fails in since 180d665d19fea419235ea173dce8b4f4e8


From: Sven Schober
Subject: [bug #66438] configure fails in since 180d665d19fea419235ea173dce8b4f4e8a5cf65
Date: Wed, 13 Nov 2024 15:16:58 -0500 (EST)

URL:
  <https://savannah.gnu.org/bugs/?66438>

                 Summary: configure fails in since
180d665d19fea419235ea173dce8b4f4e8a5cf65
                   Group: GNU roff
               Submitter: sschober
               Submitted: Wed 13 Nov 2024 08:16:54 PM UTC
                Category: General
                Severity: 3 - Normal
              Item Group: Build/Installation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 13 Nov 2024 08:16:54 PM UTC By: Sven Schober <sschober>
Hi!

Since commit 180d665d19fea419235ea173dce8b4f4e8a5cf65:


commit 180d665d19fea419235ea173dce8b4f4e8a5cf65
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Thu Oct 24 13:27:43 2024 -0500

    XXX version validity check


configure fails form me on mac os with the following error:


./configure --without-x --with-uchardet CPPFLAGS="-I/opt/homebrew/include"
checking checking that groff version string has valid format... 1.23.0
invalid
configure: groff's version string must start with three decimal
integers separated by dots.  "1.23.0" does not match.

configure: error: Aborting.


I narrowed it down to this if expression failing:


if expr "$SHORT_VERSION" : '[[0-9]]\+\.[[0-9]]\+\.[[0-9]]\+' \


I think this might be because expr behaves differently on mac os than on a
linux distribution?


man expr | egrep 'against' -A1
             The “:” operator matches expr1 against expr2, which must be
a
             basic regular expression.  The regular expression is anchored to


So... expr wants a _basic_ RE
.
And inspecting re_format(7) tells me:


man re_format | grep 'are ordinary' -C2
     Obsolete (“basic”) regular expressions differ in several respects.
‘|’
     is an ordinary character and there is no equivalent for its
     functionality.  ‘+’ and ‘?’ are ordinary characters, and their
     functionality can be expressed using bounds (‘{1,}’ or ‘{0,1}’
     respectively).  Also note that ‘x+’ in modern REs is equivalent to
‘xx*’.


I can rewrite the re to:


expr "$SHORT_VERSION" : '[0-9]\{1,\}\.[0-9]\{1,\}\.[0-9]\{1,\}'
6


But I do not know, if this is still matching on other machines.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66438>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]