mandoc @1.14.3: not using the right compiler

[ryandesign (Ryan Carsten Schmidt)]

Actually it's not specific to the universal variant. Rather, the problem is that the port is not UsingTheRightCompiler. I had my MacPorts configured to error out if cc is used, using the method described at UsingTheRightCompiler#testing. Perhaps the portfile code that set CC that was removed in [14f7de9e9ad521cce6389678675706e8593b9834/macports-ports] was needed after all.

[grimreaper (Eitan Adler)]

Ugh. I'll take a look. Thanks for the report. Overall this port has been quite painful :\

Also that testing method seems useful. I'll configure my system as such

[grimreaper (Eitan Adler)]

I configured my system the same way as in the wiki:

sudo svn checkout https://svn.macports.org/repository/macports/users/ryandesign/no_default_gcc /opt/local/bin/no_default_gcc

and then modifying my macports.conf.

With this configuration I can not replicate the error you found unless I use the universal variant:

[21397 23:46:24.450 eax@FlyingEagle ...ports/textproc/mandoc !2!]∴sudo port install        (git:ports)-[master]
--->  Fetching archive for mandoc
--->  Attempting to fetch mandoc-1.14.3_3.darwin_17.x86_64.tbz2 from https://packages.macports.org/mandoc
--->  Attempting to fetch mandoc-1.14.3_3.darwin_17.x86_64.tbz2.rmd160 from https://packages.macports.org/mandoc
--->  Installing mandoc @1.14.3_3
--->  Activating mandoc @1.14.3_3

[21401 23:49:43.854 eax@FlyingEagle ...rts/ports/textproc/mandoc]∴sudo port install +universal           (git:ports)-[master]
--->  Fetching archive for mandoc
--->  Attempting to fetch mandoc-1.14.3_3+universal.darwin_17.i386-x86_64.tbz2 from https://packages.macports.org/mandoc
--->  Attempting to fetch mandoc-1.14.3_3+universal.darwin_17.i386-x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/mandoc
--->  Attempting to fetch mandoc-1.14.3_3+universal.darwin_17.i386-x86_64.tbz2 from http://ywg.ca.packages.macports.org/mirror/macports/packages/mandoc
--->  Fetching distfiles for mandoc
--->  Verifying checksums for mandoc
--->  Extracting mandoc
--->  Configuring mandoc
Error: Failed to configure mandoc, consult /opt/local/var/macports/build/_Users_eax_svn_macports_ports_textproc_mandoc/mandoc/work/mandoc-1.14.3/config.log
Error: Failed to configure mandoc: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_Users_eax_svn_macports_ports_textproc_mandoc/mandoc/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port mandoc failed
sudo port install +universal 1.18s user 1.82s system 62% cpu 4.833 total; max RSS 65912Ki

Fixing

[grimreaper (Eitan Adler)]

In bbb2f5e848b48590388475544f3f07e4f8814910/macports-ports:

mandoc: fix universal build; use https

Revert "mandoc: don't repeat the ./configure's job"
This reverts commit 14f7de9e9ad521cce6389678675706e8593b9834.

Fixes: #55884

[janstary (Jan Starý)]

Replying to grimreaper:

Ugh. I'll take a look. Thanks for the report. Overall this port has been quite painful :\

I'll gladly take maintainership if you want or find mandoc difficult. I find it one of the easiest pieces of software to work with.

[ryandesign (Ryan Carsten Schmidt)]

Remember to use WikiFormatting when writing in Trac so your posts are legible. I have corrected your formatting above.

Replying to grimreaper:

With this configuration I can not replicate the error you found unless I use the universal variant:

When not using the universal variant, you received a binary from our build server; your computer did not attempt to build the port from source, so you did not notice the problem. You can tell MacPorts not to look for a binary from our server by using the -s flag.

We don't normally build non-default variants on the build server, which is why when you requested the non-default universal variant, you didn't get a binary, and a from-source build was attempted automatically.