Re: [Nautilus-list] problems building from cvs
- From: Ryan Muldoon <rpmuldoon students wisc edu>
- To: Darin Adler <darin eazel com>
- Cc: Nautilus <nautilus-list lists eazel com>
- Subject: Re: [Nautilus-list] problems building from cvs
- Date: 28 Apr 2001 18:00:39 -0400
Here is the output of autogen.sh when I try and build nautilus from cvs:
[ryan luminosity nautilus]$ ./autogen.sh
I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command line.
Running gettextize... Ignore non-fatal messages.
rm: /home/ryan/tmp/nautilus/applets: is a directory
rm: /home/ryan/tmp/nautilus/components: is a directory
rm: /home/ryan/tmp/nautilus/cut-n-paste-code: is a directory
rm: /home/ryan/tmp/nautilus/CVS: is a directory
rm: /home/ryan/tmp/nautilus/data: is a directory
rm: /home/ryan/tmp/nautilus/docs: is a directory
rm: /home/ryan/tmp/nautilus/eazel-logos: is a directory
rm: /home/ryan/tmp/nautilus/hack-macros: is a directory
rm: /home/ryan/tmp/nautilus/help: is a directory
rm: /home/ryan/tmp/nautilus/helper-scripts: is a directory
rm: /home/ryan/tmp/nautilus/helper-sripts: is a directory
rm: /home/ryan/tmp/nautilus/helper-utilities: is a directory
rm: /home/ryan/tmp/nautilus/icons: is a directory
rm: /home/ryan/tmp/nautilus/idl: is a directory
rm: /home/ryan/tmp/nautilus/intl: is a directory
rm: /home/ryan/tmp/nautilus/libnautilus: is a directory
rm: /home/ryan/tmp/nautilus/libnautilus-adapter: is a directory
rm: /home/ryan/tmp/nautilus/libnautilus-extensions: is a directory
rm: /home/ryan/tmp/nautilus/librsvg: is a directory
rm: /home/ryan/tmp/nautilus/nautilus-installer: is a directory
rm: /home/ryan/tmp/nautilus/nautilus-widgets: is a directory
rm: /home/ryan/tmp/nautilus/omf-install: is a directory
rm: /home/ryan/tmp/nautilus/po: is a directory
rm: /home/ryan/tmp/nautilus/src: is a directory
rm: /home/ryan/tmp/nautilus/test: is a directory
rm: /home/ryan/tmp/nautilus/tools: is a directory
rm: /home/ryan/tmp/nautilus/ui: is a directory
rm: /home/ryan/tmp/nautilus/user-guide: is a directory
cp: *: No such file or directory
cp: /home/ryan/tmp/nautilus/applets: omitting directory
cp: /home/ryan/tmp/nautilus/components: omitting directory
cp: /home/ryan/tmp/nautilus/cut-n-paste-code: omitting directory
cp: /home/ryan/tmp/nautilus/CVS: omitting directory
cp: /home/ryan/tmp/nautilus/data: omitting directory
cp: /home/ryan/tmp/nautilus/docs: omitting directory
cp: /home/ryan/tmp/nautilus/eazel-logos: omitting directory
cp: /home/ryan/tmp/nautilus/hack-macros: omitting directory
cp: /home/ryan/tmp/nautilus/help: omitting directory
cp: /home/ryan/tmp/nautilus/helper-scripts: omitting directory
cp: /home/ryan/tmp/nautilus/helper-sripts: omitting directory
cp: /home/ryan/tmp/nautilus/helper-utilities: omitting directory
cp: /home/ryan/tmp/nautilus/icons: omitting directory
cp: /home/ryan/tmp/nautilus/idl: omitting directory
cp: /home/ryan/tmp/nautilus/intl: omitting directory
cp: /home/ryan/tmp/nautilus/libnautilus: omitting directory
cp: /home/ryan/tmp/nautilus/libnautilus-adapter: omitting directory
cp: /home/ryan/tmp/nautilus/libnautilus-extensions: omitting directory
cp: /home/ryan/tmp/nautilus/librsvg: omitting directory
cp: /home/ryan/tmp/nautilus/nautilus-installer: omitting directory
cp: /home/ryan/tmp/nautilus/nautilus-widgets: omitting directory
cp: /home/ryan/tmp/nautilus/omf-install: omitting directory
cp: /home/ryan/tmp/nautilus/po: omitting directory
cp: /home/ryan/tmp/nautilus/src: omitting directory
cp: /home/ryan/tmp/nautilus/test: omitting directory
cp: /home/ryan/tmp/nautilus/tools: omitting directory
cp: /home/ryan/tmp/nautilus/ui: omitting directory
/usr/bin/gettextize: cd: intl: No such file or directory
cp: *: No such file or directory
/usr/bin/gettextize: cd: ../po: No such file or directory
rm: /home/ryan/tmp/nautilus/po/CVS: is a directory
cp: *: No such file or directory
sed: can't read aclocal.m4: No such file or directory
You should update your own `aclocal.m4' by adding the necessary
macro packages gettext.m4, lcmessage.m4 and progtest.m4 from
the directory `/usr/share/aclocal'
Running xml-i18n-toolize
xml-i18n-toolize: `configure.in' does not exist
Try `xml-i18n-toolize --help' for more information.
Running libtoolize
libtoolize: `configure.in' does not exist
Try `libtoolize --help' for more information.
aclocal: couldn't open `configure.in': No such file or directory
/usr/bin/m4: configure.in: No such file or directory
automake: couldn't open `configure.in': No such file or directory
autoconf: configure.in: No such file or directory
./autogen.sh: ./configure: No such file or directory
Now type 'make' to compile nautilus.
On 22 Apr 2001 21:55:29 -0700, Darin Adler wrote:
> on 4/22/01 3:30 PM, Ryan Muldoon at rpmuldoon students wisc edu wrote:
>
> > I am having trouble with the autogen.sh script when I do a fresh
> > checkout of nautilus from cvs. I have the suggested versions of
> > automake and autoconf, so I am not quite sure what is wrong. Basically,
> > what happens is that configure.in gets deleted somewhere during the
> > execution of the script, so autoconf can't make a configure script. As
> > a result, automake can't run, and I don't have any Makefiles. Is there
> > a solution to this problem? I'd imagine that it is something dumb and
> > common that I am just not noticing. I'd really appreciate some help, as
> > doing this is kind of impeding my ability to test a patch I made.
>
> There's no dumb common error I know of that leads to this problem. To help,
> I'd need a bit more to go on than this high-level description.
>
> > Also - is there something like eazel-hacking for general consumption?
>
> Many folks outside Eazel use eazel-hacking, but I'm not sure you'd like it.
> It has a lot of "opinions" about how you set up your system.
>
> > I'd like to be able to try and mess around with working on Nautilus more
> > often, especially as my semester is over in a few weeks. But, I'd
> > prefer to keep testing/source builds seperate from my "stable"
>
> My solution to this problem is to work without a file manager, so I have no
> "stable" version of Nautilus at all. Given how Nautilus uses CORBA, I think
> this is the only practical solution. The two copies of Nautilus are not
> going to stay out of each other's way.
>
> -- Darin
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]