[Nexus-developers] Linux Debian etch & nexus 4.0rc2 testing results

[Akeroyd, FA (Freddie)]

Rudi,

The fortran bindings are not built by default ... you need to pass -with-f77 and/or -with-f90 to configure. The F90 bindings work with g95, but might need gfortran 4.2 or above. In NeXus 3.0 the fortran bindings were built by default, but we had a few problems with configure picking up the wrong or a non-working compiler on some systems when most of the time people were not interested in the fortran bindings.

I have had a look at psrc.tar.gz and your changes seem reasonable. I think they do, however, raise the issue of package naming, which is something that we have been meaning to look at for some time. Currently our source and binary packages are both called "nexus". For your debian binary packages you have named the source package "libnexus" and split the binaries into "libnexus4", "libnexus-dev" and "libnexus-tools". Did you choose the name "libnexus" as there was a problem with using "nexus", or did you think "libnexus" was a more appropriate/descriptive name? I'm wondering if it might cause confusion with having the debian package called "libnexus" and the rpm "nexus" - if "nexus" is already used elsewhere as a package name then maybe we need to have a general developer discussion on changing our rpm package name to libnexus too.

Regards,

Freddie

________________________________________
From: Rudi Cilibrasi, Ph.D. [mailto:cilibrar at gmail.com] 
Sent: 02 April 2007 08:48
To: Akeroyd, FA (Freddie); nexus-developers at nexusformat.org
Subject: Re: [Nexus-developers] Linux Debian etch & nexus 4.0rc2 testing results

Hi Freddie,

I have investigated further and verified your hypothesis is accurate.  I have therefore built a new version of the libmxml package (it is only upstream version 2.2 in the official Debian archive) based on the new 2.2.2 upstream libmxml version.
I have also updated my Debian package for libnexus for the new 4.0.rc2 release.  I ran into a few issues but overall the build was successful.

1) I had to change the version from 4.0.rc2 to 4.0.0 to avoid breaking some version-soname awk code.
2) I had to add SONAME setting code in configure.ac and src/Makefile.am to allow for better linking and library hygeine. 
3) I could not build the fortran bindings this time for some reason.  It seems not to even try to build them with a normal make.  If I go into the f77 or f90 directories myself I get a message like this:
L-(09:20:%)-- m                                                --(Mon,Apr02)-XJ 
/bin/sh ../../libtool --mode=compile    -c -o napif.lo napif.f
libtool: unrecognized option `-c'
Try `libtool --help' for more information.
make: *** [napif.lo] Error 1

I have included many updated Debian packages for libmxml as well as libnexus (all based on 4.0.rc2 orig) and also tarred up all the source files I used (modified/added) to make the package.  Could you please review the files I had to change so that we can decide which, if any, of the diffs are appropriate to add to your main codebase?  It is in psrc.tar.gz and the
whole load of files is in:
http://cilibrar.com/~cilibrar/projsup/nex4/
If you would prefer not to receive patches through email/web post like the above then I am also willing to become a developer on tigris and just use Subversion directly if that is more convenient for you.  I look forward to your response and hope to continue to help you improve 4.0.  Best regards,

Rudi
On 4/1/07, Akeroyd, FA (Freddie) < F.A.Akeroyd at rl.ac.uk> wrote:
Rudi,
 
Thank you for downloading and testing 4.0rc2 I have looked at the bug tracker logs and the reason you were unable to register and add an issue was because you were giving your username as "cilibrar" rather than "Cilibrar". I though the usernames were case insensitive, but it appears this is not the case...
 
I believe the test failure for XML is related to the "mxml" package provided by Debian. NeXus makes use of the "custom nodes" feature in mxml, and a bug was fixed for these in version 2.2.2 I'm not sure whether the Debian provided version is either pre 2.2.2 or has some other issue, but when I removed the "libxml-dev" and "libmxml1" packages from an old Debian system I have and installed mxml-2.2.2 from source (http://www.easysw.com/~mike/mxml) the tests were passed. Thank you for bringing this issue to our attention - we will add a note to the next distribution's README files.
 
Regards,
 
Freddie     
 
P.S. While checking out the above I also found an issue with the -with-xml configure option  ... it sets CFLAGS correctly, but due to a typo not the LDFLAGS. This is now fixed in the 4.0 branch and will be in a future update
 
________________________________________
From: nexus-developers-bounces at nexusformat.org [mailto:nexus-developers-bounces at nexusformat.org] On Behalf Of Rudi Cilibrasi, Ph.D.
Sent: 31 March 2007 16:10
To: nexus-developers at nexusformat.org
Subject: [Nexus-developers] Linux Debian etch & nexus 4.0rc2 testing results
 
Hi everybody,

I tried to register and add an 'issue' to the bug tracker but so far it doesn't seem to let me in.  I have already verified my email...
So I will just send my results here instead.  I am using an x86 Linux Debian etch system.  make check failed with 
2 failed tests and 3 skipped.
  To: <nexus-developers at nexusformat.org>
   Subject: [NeXus Library 4.0rc2] testsuite: 5 6 failed

I attach the testsuite.log in this email.  Note also that I got several compile warnings and these I have logged in another attached file, "o".
Cheers,

Rudi


-- 
Democracy is two wolves and a sheep deciding what to eat for lunch. 
Liberty is a well-armed sheep contesting the vote. 



-- 
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.