[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: how to perverse file permission in subversion

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-08-16 09:34:33 CEST

On Aug 15, 2007, at 22:43, ying lcs wrote:

> Actually, I have this weird problem.
>
> I am able to build a program in RedHat EL4 in a directory using
> configure and then install.
>
> Then I check in the directory to svn and checkout again.
>
> And when I try to build, it does not build, it get error like this:
>
> configure.ac:360: the top level
> configure.ac:360: warning: AC_RUN_IFELSE was called before
> AC_GNU_SOURCE
> configure.ac:5452: error: possibly undefined macro: AM_PATH_LIBGCRYPT
> If this token and others are legitimate, please use
> m4_pattern_allow.
> See the Autoconf documentation.
> make[3]: *** [Makefile.am] Error 1
> make[3]: Leaving directory
> `/root/video_offical_working_dir5/video/vlc/modules/access'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/root/video_offical_working_dir5/video/
> vlc/modules'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/video_offical_working_dir5/video/
> vlc'
> make: *** [all] Error 2

Sorry, I don't know what that means.

Try taking Subversion out of the picture. Can you build the software
properly before checking it into Subversion? If not, talk to the
developers of that software.

If checking it into Subversion really is what breaks it, then do an
"svn export" from the repository. Can you build that? If not, do a
recursive diff between the directory before it was checked into
Subversion and the export. What's different?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 16 09:33:24 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.