-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/14/11 4:35 PM, Julius Canute wrote:
> Hi
> I am trying to update existing camlimges to version 4.0.0.
> HomePage:http://gallium.inria.fr/camlimages/
> DownloadUrl:https://bitbucket.org/camlspotter/camlimages/get/camlimages-4.0.0.tar.bz2
> 
> There is a problem while configuring camlimages:
> 
> config.status: error: cannot find input file: doc/Makefile.in
> 
> inorder to resolve it i removed line 524 in configure.ac which specifies
> "doc/Makefile"
> and compiled manually which worked fine.
> 
> But if the same i did it in fink using sed in patchscript:
> 
>  sed -i -e '524d' camlimages/configure.ac
> 
> I still get the error:
> config.status: error: cannot find input file: doc/Makefile.in
> 
> What might be the problem?
> Camlimages is a library, i think the old package does not follow the
> current policy for packaging libraries. Will it be fine if i edit the
> existing camlimages or should i create a new package?
> 
> Regards
> A.Julius Canute
> 
> 
> 

Have you contacted the listed maintainer for that package to make sure
that he agrees to let you update it.

- -- 
Alexander Hansen, Ph.D.
Fink User Liaison
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1Zpg8ACgkQB8UpO3rKjQ8YtACdH4ZTNq19b9bWWHi1eB5mSEM5
wjkAn3N1PlzvKkKvd3YXrabqKMINn6H5
=Kxie
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to