Bug 829106 – net-proxy/privoxy-3.0.33 - configure: WARNING: unrecognized options: --disable-static

• Status: CONFIRMED
• Product: Gentoo Linux

[Description Toralf Förster 2021-12-13 18:04:37 UTC]

configure: WARNING: unrecognized options: --disable-static

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_no_multilib-j4-20211209-113836

  -------------------------------------------------------------------

  The log matches a QA pattern or a pattern requested by a Gentoo developer.

[Comment 1 Toralf Förster 2021-12-13 18:04:39 UTC]

Created attachment 758829 [details]
emerge-history.txt

[Comment 2 Toralf Förster 2021-12-13 18:04:40 UTC]

Created attachment 758830 [details]
etc.portage.tar.bz2

[Comment 3 Toralf Förster 2021-12-13 18:04:41 UTC]

Created attachment 758831 [details]
net-proxy:privoxy-3.0.33:20211213-174740.log

[Comment 4 Andrew Savchenko 2021-12-13 19:07:48 UTC]

--disable-static is enforced by portage, not by ebuild.

Upstream doesn't support this option because it provides no libraries or statically build binaries.

So either portage should not enforce this option everywhere, or QA check should ignore this warning for --disable-static option.

[Comment 5 Mike Gilbert 2021-12-13 21:01:02 UTC]

The portage behavior is specified by PMS. There is nothing the portage team can really do about it.

See also bug 814368.

[Comment 6 Michał Górny 2021-12-13 21:05:07 UTC]

I'm guessing this is because of:

  --enable-static-linking         Use static linking instead of dynamic linking (ie. LDFLAGS=-static)

[Comment 7 Mike Gilbert 2021-12-13 21:07:43 UTC]

I think it would be acceptable to ignore this bug report until a new EAPI provides a way to resolve it.