-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mark Ellis wrote: > On Mon, 2009-01-26 at 21:39 +0100, Federico Ferri wrote: sorry > Mark, > > I tried with synce-gvfs 0.2.1 with and without --with-gvfs-source > option. > > without that option it compiles fine, but with your gvfs-tree. when > I use the option (actually with a gvfs-1.0.3 tree) it fails in make > dist, which makes the whole build fail. > > attached the two logfiles (successful and unsuccessful build) > > > >> It's because we're treating the gvfs source as part of our tree, > so it's >> using relative paths, and passing an absolute path to configure. > Can you >> pass a relative path ?
not properly (it is not assured that portage unpacks the synce-gvfs tarball and the gvfs tarball in the same directory level.) but I used a symbolic link (with absolute path) - that made the trick :-) thank you Federico Ferri -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl+aSUACgkQV/B5axfzrPs17QCfQ7uG+G8K4wMFMbsbwrvucy0D ALoAn1YtelnXXaTg13cblUk2nOV3T7qY =aOEi -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
