> On Sun, May 03, 2009 at 03:22:45PM -0500, Christopher Stover wrote:
> > I'm back to trying to build the latest git, but I'm not seeing the
> > snapshot.sh anywhere. I ran 'git clone git://repo.or.cz/barry.git
> > scripts' and looked in the scripts directory. You'll have to forgive me,
> > I'm not very experienced with git so I could easily be missing something.
>
> That clone gives you the default master branch, with 'scripts' as the target
> directory.
>
> You want to look at all the branches:
>
> git branch -a
>
> You should see an origin/scripts in there. You can checkout that branch with:
>
> git checkout origin/scripts
>
> This will give you an entirely different tree. :-) I have barry cloned
> twice on my system, with the scripts branch checked out in one directory
> so they are available fr use, and the Barry tree in the other. By putting
> scripts into a branch, it keeps everything related to Barry inside the Barry
> source repo.
>
Thanks for the help with this Chris. I've used git very little, but that was
very helpful.
>
> > Generating logs.html
> > Warning: Tag `USE_WINDOWS_ENCODING' at line 64 of file Doxyfile has become
> > obsolete.
> > To avoid this warning please update your configuration file using "doxygen
> > -u"
> > Warning: Tag `DETAILS_AT_TOP' at line 156 of file Doxyfile has become
> > obsolete.
> > To avoid this warning please update your configuration file using "doxygen
> > -u"
> > Warning: Tag `MAX_DOT_GRAPH_WIDTH' at line 1189 of file Doxyfile has become
> > obsolete.
> > To avoid this warning please update your configuration file using "doxygen
> > -u"
> > Warning: Tag `MAX_DOT_GRAPH_HEIGHT' at line 1197 of file Doxyfile has
> > become obsolete.
> > To avoid this warning please update your configuration file using "doxygen
> > -u"
>
> This must be due to your using Rawhide? My version of doxygen is 1.5.6.
>
Yes, you are correct. I'm using doxygen-1.5.8 right now.
>
> > libtoolize: You should add the contents of the following files to
> > `aclocal.m4':
> > libtoolize: `/usr/share/aclocal/libtool.m4'
> > libtoolize: `/usr/share/aclocal/ltoptions.m4'
> > libtoolize: `/usr/share/aclocal/ltversion.m4'
> > libtoolize: `/usr/share/aclocal/ltsugar.m4'
> > libtoolize: `/usr/share/aclocal/lt~obsolete.m4'
>
> That's odd. I thought running aclocal was supposed to take care of things
> like this automatically.
>
Unfortunately, I haven't a clue. I don't know anything about aclocal, but let
me know if there's anything I can do to help figure out why it's complaining.
>
> > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> >
> > libtoolize: rerunning libtoolize, to keep the correct libtool macros
> > in-tree.
>
> I added this to the latest git tree. You may need to do a 'git pull' to
> make sure you have the latest. My latest commit to Barry was on
> May 1, 23:08. If you don't see that in your 'git log' output, you're
> not working with the latest.
>
My latest git pull shows changes from May 6th, but I'm still getting these
messages from libtoolize.
Finally, I have everything building well, but I'm running into a problem with
rpmlint. It's giving me the following warnings:
barry.i386: W: unstripped-binary-or-object /usr/sbin/breset
barry.i386: W: unstripped-binary-or-object /usr/bin/barrybackup
barry.i386: W: unstripped-binary-or-object /usr/bin/bidentify
barry.i386: W: unstripped-binary-or-object /usr/sbin/pppob
barry.i386: W: unstripped-binary-or-object /usr/bin/btranslate
barry.i386: W: unstripped-binary-or-object /usr/bin/btool
barry.i386: W: unstripped-binary-or-object /usr/bin/bktrans
barry.i386: W: unstripped-binary-or-object /usr/bin/bfuse
barry.i386: W: unstripped-binary-or-object /usr/sbin/bcharge
barry.i386: W: unstripped-binary-or-object /usr/bin/brecsum
barry.i386: W: unstripped-binary-or-object /usr/bin/bjavaloader
barry.i386: W: unstripped-binary-or-object /usr/bin/brimtrans
barry.i386: W: unstripped-binary-or-object /usr/bin/upldif
barry.i386: W: unstripped-binary-or-object /usr/bin/bs11nread
barry-libs.i386: W: unstripped-binary-or-object /usr/lib/libbarry.so.0.0.15
Any clue as to why I would be seeing this? I don't recall seeing this issue
with the last working build I did (a long time ago back in January).
Finally, Fedora requires me to remove any *.la and *.a files. I'm just doing
this in the spec file with %{__rm} -rf %{buildroot}%{_libdir}/*.la. Is there
any way for me to build without creating these?
Thanks,
Chris
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
