Ken McDonell <kenj@xxxxxxxxxxxxxxxx> writes:
> Recent commits have added libmicrohttpd to the build dependencies.
> This is not available on all platforms, e.g. SuSE 12.1, CentOS 5.9,
> Mac OS X, ... and/or not installed on my machines.
That's fine; the autoconf configury will arrange to omit that part.
> [...]
> But for the RPM and dpkg builds the dependency is apparently
> hard-coded in the package specifications, and so the build dies a
> horrible death.
>
> Is this fixable?
How do you mean by fix? The RPM & DPKG builds are meant to simulate a
distributor's official builds, which would have the libmicrohttpd
stuff available. One can't make those control files conditional on
the environment, otherwise the builds wouldn't be reproducible.
With RPM, it is possible to pass conditionals from the rpm command
line (--with-FOO), which macros in the .spec can adapt to, and turn
features on or off. I don't know whether DPKG can do that. If so, we
could add such a knob, just for people who use these RPM/DPKG files as
non-distributors.
> I really don't want to try and build libmicrohttpd from source on half
> a dozen (so far) machines.
(What OS do these run?)
- FChE
|