[Rivet] pkgpath

[James Monk]

I've found that configure only finds fastjet-config if I add --with- 
fastjet=/usr/local to configure.  Surely it should look there anyway?

Another problem that this has shown up is the testing of the fastjet  
version evaluates the version variable as a string and so the test  
always evaluates false, i.e. configure gives me the incredibly  
annoying error

	checking FastJet version using fastjet-config... 2.4.0
	configure: error: FastJet version 2.4.0 or later is required

I've found that this test in configure.ac actually works:

	case "$fjversion" in
   		1.*|2.0.*|2.1.*|2.2.*|2.3.*)
     			AC_MSG_ERROR([FastJet version 2.4.0 or later is required])
     			;;
   		*)
     			;;
	esac

James

On 24 Apr 2009, at 11:53, James Monk wrote:

> Hi Andy,
>
> I haven't installed the newest Fastjet yet and so Rivet configuration
> should fail for me (since I have fastjet-config in /usr/local/bin),
> but it doesn't and I get a compiler error instead.  In order to use
> fastjet-config to determine the fastjet version the path to fastjet
> must be set.
>
> It looks to me like the package path for fastjet isn't getting set,
> but it is still building because it is in a standard location.  If I
> add AC_MSG_NOTICE([$FASTJETPATH]) immediately after the
> AC_CEDAR_LIBRARYANDHEADERS call for fastjet (configure.ac:78) then I
> get a blank line, same as if I add AC_MSG_NOTICE([$pkgpath]) to the
> end of AC_CEDAR_LIBRARYANDHEADERS (pkgchecks.m4:94).
>
> This makes me wonder if pkgpath is getting set at all.  Can anyone
> more expert than me in autotools comment?
>
> cheers,
>
> James
>
>
>
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet