serf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: Please consider dropping scons
Date Tue, 22 Aug 2017 08:39:17 GMT
Hello, fellow Austin-ite!

In the past, serf had three separate build systems: custom, autoconf, and
[Windows] Make. We got rid of all of those systems, and went with a
singular replacement: SCons. Yeah, it kinda sucks that HP-UX doesn't have
very good support to bootstrap this build environment. But over the past
fifteen years, serf has tried them all. Maintaining multiple systems was
much more difficult than consolidating around SCons (and its own

Switching to an autoconf-based system leaves out Windows developers, so it
is kind of a non-starter.


On Mon, Aug 21, 2017 at 7:01 PM, Michael Schultz <> wrote:

> I have just spent the last two days trying to build serf on an HP-UX
> machine. I was trying to build Subversion on the machine, and everything
> was going along fine until I tried to build serf. Then I had to install
> scons, which required me to build python, which paradoxically required
> python to be already installed on the machine. I got around all of that but
> then when I returned to serf, now scons can’t locate the C compiler. I have
> found topics online that tell me now to set the external PATH, but they all
> assume that I know something about scons, which I don’t, and thus their
> sage advice is of no help.
> So, I am NOT asking for help on that. I have now exceeded my time on this
> side project, and must solve my problem with subversion by building the
> source on a separate LINUX machine where the subversion client works
> properly and just copying the source over to the HP-UX machine.
> What I am asking is that you drop scons as the build environment and
> switch to configure, like the rest of the Apache projects.
> *Michael Schultz*
> Software System Developer – Senior Principal
> Micro Focus
> 8310 N. Capital of Texas Highway
> Building 1, Suite 155
> Austin, TX 78731, USA
> (P)+1 512.340.4823 <(512)%20340-4823>
> (F)+1 512.340.1331 <(512)%20340-1331>
> Fuze x124823
> ------------------------------
> [image:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message