Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: nroff requirement
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Gustafsson via curl-library <curl-library_at_lists.haxx.se>
Date: Fri, 28 Oct 2022 21:43:14 +0200
> On 28 Oct 2022, at 19:05, Christian Weisgerber via curl-library <curl-library_at_lists.haxx.se> wrote:
>
> curl's configure script checks for nroff and disables the built-in
> manual if no nroff is found. However, if you build curl from a
> release tarball, nroff is never actually run because a pre-built
> tool_hugehelp.c file is already included, obviating the need to
> generate that file with nroff.
The testsuite also use nroff.
> So maybe the requirement for nroff should be relaxed if tool_hugehelp.c
> is already included?
We could relax it to issue a warning, but still allow configure to carry-on
even with USE_MANUAL. For reference, the postgres project does a similar thing
for bison, which is not needed when building from a release tarball. The below
is output from configure in case bison isn't found:
if test -z "$BISON"; then
AC_MSG_WARN([
*** Without Bison you will not be able to build PostgreSQL from Git nor
*** change any of the parser definition files. You can obtain Bison from
*** a GNU mirror site. (If you are using the official distribution of
*** PostgreSQL then you do not need to worry about this, because the Bison
*** output is pre-generated.)])
Gating it on the existence of tool_hugehelp.c might just be complication
without benefit though, probably better to just always do it.
Date: Fri, 28 Oct 2022 21:43:14 +0200
> On 28 Oct 2022, at 19:05, Christian Weisgerber via curl-library <curl-library_at_lists.haxx.se> wrote:
>
> curl's configure script checks for nroff and disables the built-in
> manual if no nroff is found. However, if you build curl from a
> release tarball, nroff is never actually run because a pre-built
> tool_hugehelp.c file is already included, obviating the need to
> generate that file with nroff.
The testsuite also use nroff.
> So maybe the requirement for nroff should be relaxed if tool_hugehelp.c
> is already included?
We could relax it to issue a warning, but still allow configure to carry-on
even with USE_MANUAL. For reference, the postgres project does a similar thing
for bison, which is not needed when building from a release tarball. The below
is output from configure in case bison isn't found:
if test -z "$BISON"; then
AC_MSG_WARN([
*** Without Bison you will not be able to build PostgreSQL from Git nor
*** change any of the parser definition files. You can obtain Bison from
*** a GNU mirror site. (If you are using the official distribution of
*** PostgreSQL then you do not need to worry about this, because the Bison
*** output is pre-generated.)])
Gating it on the existence of tool_hugehelp.c might just be complication
without benefit though, probably better to just always do it.
-- Daniel Gustafsson https://vmware.com/ -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-10-28