On Thu, Jun 8, 2017 at 12:22 PM, Dennis Clarke <dcla...@blastwave.org> wrote:
> On 06/08/2017 10:56 AM, William A Rowe Jr wrote:
>>
>> On Wed, Jun 7, 2017 at 9:44 PM, Dennis Clarke <dcla...@blastwave.org>
>> wrote:
>>>
>>> On 06/07/2017 08:16 PM, William A Rowe Jr wrote:
>>>>
>>>>
>>>> As I said... checking out and building 'your own tarball' on a
>>>> conventional system absolutely beats convincing AIX, Solaris
>>>
>>>
>>> By "conventional" I think you mean "Linux" or anything with a reasonable
>>> GNU toolchain and we all know that won't happen from IBM or Oracle. At
>>> all. Lucky for me I have the latest perl, autoconf, m4 and such built
>>> already and "python" still blows up neatly in any attempt to build from
>>> sources. Don't even ask about PHP ver 7.x where code really gets
>>> gnuified and ugly.
>>
>>
>> Correct, a typical dev environment with a rather complete toolchain.
>
>
> Note: I am not being a barking dog.  I really am concerned.  Long term.

Let me repeat; our buildconf toolchain use will not change, *because this
is not required on a build system*. What I'm describing is the packaging
step. If you can get the autoconf, m4, libtool, and python to all play nice,
our ./buildconf script will work (you might need to reorder your path to
dodge the dodgy flavors of scripts on some of these oddball un*xes.)

But even if you don't want to fight that battle on lots of different platforms,
all ./buildconf does is to provide a ./configure script. Once you do that
step on a machine that does have this whole toolchain, it is a matter
of tarring up that image and taking it to any of the platforms you noted.
Now, ./configure aught to be a very portable script. Bug reports should
go to the autoconf project, libtool project, or apr project as appropriate,
depending on what the error is exactly.

It's not perfect, but we are going on nearly 20 years of success, since
we've dodged the real nightmares such as --enable-maintainer-mode
automake features which cause you to need that whole toolchain,
just because of lost datestamps and the like.

Reply via email to