Hi Brian,
Yes, there clearly is some "consolidation" work to be done on
xrootd... This framework has been put in place to detect such problems
early and testing is, of course, a logical next step. I have been
already looking into that: we have a nice testing framework written
for Castor and based on py.test that would fit nicely into the
buildbot infrastructure. Writing those tests, however, takes time and
I also have a couple of other projects that wouldn't mind some loving
:)
Cheers,
Lukasz
On Sat, Oct 23, 2010 at 2:16 AM, Brian Bockelman <[log in to unmask]> wrote:
> Hi Lukasz,
>
> Is there any automated testing in addition to the building?
>
> I was on an airplane today and found there are a few things (such as XrdSecssl) that don't work on Mac OS X with autotools. Our Mac builds produce *.dylib, while the XrdCryptoFactory assumes *.so.
>
> Additionally, the linker on the Mac didn't like the resulting libXrdOfs (it had a few missing symbols which are in libXrdOss but weren't linked).
>
> So, everything built fine, but I couldn't even start up a simple test case.
>
> Brian
>
> On Oct 22, 2010, at 10:42 AM, Lukasz Janyst wrote:
>
>> Hi Derek,
>>
>> On Fri, Oct 22, 2010 at 4:44 PM, Derek Feichtinger
>> <[log in to unmask]> wrote:
>>> Autotools would have been an ideal solution for a multiarchitecture build
>>> test system with a common source tree on a shared FS. I had proposed that at
>>> this time. But the tools age, and I do not think that the autotools build
>>> has any backup inside of the xrootd developers. So I am also a bit reluctant
>>> to put more time into it at this stage.
>>
>> Actually, I would like to migrate to CMake, but I don't really have
>> time to look into that at the moment. I use autotools because it
>> supports parallel building and that makes a really big difference my
>> quad core development box :)
>>
>>> But I can have a look at your build and try to help for this problem,
>>> naturally.
>>
>> Thanks!
>>
>>> What do you see when you run ./config.guess inside the top directory on your
>>> SUN machine?
>>> Can you send me the config.log and config.status that is produced after you
>>> have run configure?
>>
>> Well, it builds fine on SPARC, but it doesn't on i386. The files
>> are attached.
>>
>> Thanks,
>> Lukasz
>> <config.status.gz><config.log.gz>
>
>
|