Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 550718 - net-libs/libmicrohttpd: enable postprocessor by default
Summary: net-libs/libmicrohttpd: enable postprocessor by default
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Anthony Basile
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-29 08:34 UTC by Patrick Lauer
Modified: 2015-07-04 19:55 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Lauer gentoo-dev 2015-05-29 08:34:54 UTC
From #gnunet:

<dduffield> Hello, I am a Gentoo user, and I have a build failure for 0.9.5a, where ld returned 1 exit status, involving undefiend reference to 'MHD_create_post_processor' in gnunet-gns-fcfsd.c
<grothoff> dduffield: yes, somehow Gentoo must have build with --disable-postprocessor or something like that, which is explicitly something distributions must NOT do. (This is an option for embedded systems where 1k of code size matters.)

Checking the ebuilds, there's a USE="messages" that controls the postprocessor feature indirectly.

This might not be an intended feature, and needlessly confuses users.
Maybe it should be uncoupled from USE="messages" and enabled unconditionally?
Comment 1 Anthony Basile gentoo-dev 2015-07-04 19:55:15 UTC
(In reply to Patrick Lauer from comment #0)
> From #gnunet:
> 
> <dduffield> Hello, I am a Gentoo user, and I have a build failure for
> 0.9.5a, where ld returned 1 exit status, involving undefiend reference to
> 'MHD_create_post_processor' in gnunet-gns-fcfsd.c
> <grothoff> dduffield: yes, somehow Gentoo must have build with
> --disable-postprocessor or something like that, which is explicitly
> something distributions must NOT do. (This is an option for embedded systems
> where 1k of code size matters.)
> 
> Checking the ebuilds, there's a USE="messages" that controls the
> postprocessor feature indirectly.
> 
> This might not be an intended feature, and needlessly confuses users.
> Maybe it should be uncoupled from USE="messages" and enabled unconditionally?

Decoupling it from messages works.  Since it failed otherwise, no rev bump needed.  Its in the tree for 0.9.42, previous unstable versions are off.  I'm opening a stablereq for 0.9.42 since its been in long enough.