"Rupert Smith" <[EMAIL PROTECTED]> wrote: > Well I was already told that having an all-in-one would be better in > the previous thread where I asked about it. Also I did a build from a > source distribution and I had to upgrade a lot more tools (on RH3) > than were mentioned in the building from source dist instruction. I > tried to make this clear in the instructions by saying: > > Building from a source distribution: > > You do not require: > > * autoconf > * automake > * JDK 5.0 > > I had to upgrade *everything* else on RH3 to do a build. In fact it > was complicated enough, that I just did a complete build from a > checkout anyway. I don't think the current README-dist instructions > are anywhere near complete enough to follow. All in one file has the
Hi Rupert, I've just tried my first qpidc-0.1 build-from-tarball on RH3 (well, actually on AS3), and the first problem is that configure doesn't find the required level of APR support. APR is a big thorn in qpidc's portability side right now (ironic, since its "P" stands for "Portable"). Last I heard, APR is slated to be removed, so I've avoided spending time to work around build problems related to its presence. If removing APR is not something we can do soon, then I may revisit it. Obviously, there are other sticks in the fire, like the 0_9->trunk merge, so may be good to wait until that's complete. I confess that making the build-from-tarball-on-RHEL-3 process easy has not been a high priority, since the focus is on modern systems. I rationalize that by saying people with older systems can follow the README-dev instructions. But this is just in the interim. I expect that before too long, even on RHEL-3, you'll be able to do the classic "./configure && make ...", and everything will just work. > advantage of files not getting out of sync with each other; I pointed > out a dependency version conflict between the existing files. > > Up to you C++ guys to decide though. I'm just trying to contribute a > set of build instructions that an occasional Linux user with rusty C++ > skills could follow. Maybe the fast-track for source distribution > builds needs to be made a little clearer? IMHO, there's no "maybe" about it :-) The build-from-tarball instructions should be dead simple. With a little effort, the code may soon be portable enough so that the dead-simple instructions will suffice.
