I've just encountered a problem building gsasl9-0.2.24-1002, and I appear
to have found a workaround.  (Maintainer CC'd).

Fink 0.28.1 (unstable source); MacOS 10.5.2 Intel; all updates applied.

With the .info file as shipped, issuing the command "fink rebuild gsasl9"
results in the following error, immediately after ./configure completes:

    make
     cd . && /bin/sh 
/sw/src/fink.build/gsasl9-0.2.24-1002/gsasl-0.2.24/build-aux/missing --run 
automake-1.10 --gnu
    Makefile.am: required file `./INSTALL' not found
    Makefile.am:   `automake --add-missing' can install `INSTALL'
    make: *** [Makefile.in] Error 1
    ### execution of make failed, exit code 2
    Removing runtime build-lock...
    Removing build-lock package...
    /sw/bin/dpkg-lockwait -r fink-buildlock-gsasl9-0.2.24-1002
    (Reading database ... 63605 files and directories currently installed.)
    Removing fink-buildlock-gsasl9-0.2.24-1002 ...
    Failed: phase compiling: gsasl9-0.2.24-1002 failed

The problem appears to come from line 25 of gsasl9.info:

    PatchScript: <<
    mv INSTALL INSTALL.txt
    perl -pi -e 's;gsasl_LDADD =;$& -Wl,-m;' src/Makefile.in
    perl -pi -e 's,dynamiclib,$& -single_module,' {,lib/}{aclocal.m4,configure}
    <<

If I comment out the "mv INSTALL INSTALL.txt" command, then the package
builds successfully, but installation fails:

    /usr/bin/install -d -m 700 
/sw/src/fink.build/root-gsasl9-0.2.24-1002/sw/share/doc/gsasl9
    /bin/cp -r INSTALL.txt 
/sw/src/fink.build/root-gsasl9-0.2.24-1002/sw/share/doc/gsasl9/
    cp: INSTALL.txt: No such file or directory
    ### execution of /bin/cp failed, exit code 1
    Removing runtime build-lock...
    Removing build-lock package...
    /sw/bin/dpkg-lockwait -r fink-buildlock-gsasl9-0.2.24-1002
    (Reading database ... 63605 files and directories currently installed.)
    Removing fink-buildlock-gsasl9-0.2.24-1002 ...
    Failed: phase installing: gsasl9-0.2.24-1002 failed

To work around this problem, I changed "mv INSTALL INSTALL.txt" to
"cp INSTALL INSTALL.txt", and the package compiles and installs
successfully.  AFAICT, this isn't a problem, as INSTALL.txt is just one of
the package's documentation files and so the precise filename isn't
important.  But I'd like to know if there's a better way to fix this
problem.

Richard

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to