> On Wed, Apr 22, 2009 at 01:31:30PM -0500, Christopher Stover wrote:
>> Hi Chris,
>> I'm using gcc-4.4.0-0.34.
>
> Thanks.  Maybe I can setup a test build here, and squash some of these
> bugs early. :-)
>

Glad I could help.  In regards to using the bleeding edge Fedora, I suppose 
I am.  I run Fedora Rawhide as opposed to release versions.  I didn't even 
realize 4.4.0 was released yesterday.  I'm almost wondering if Fedora was a 
non-release version for a while considering there's 34 builds already! 
Anyway, this could explain some of the problems I'm running into while 
building.

>
>> I'm trying to create the tarball with the new git and (cd build && 
>> ../tar-create.sh 0 15) but oddly I'm getting:
>>
>> barry-0.15/maintainer/make-deb-local.sh
>> barry-0.15/maintainer/git-release-tar.sh
>> barry-0.15/maintainer/make-deb.sh
>> barry-0.15/config.h.in
>> ../tar-create.sh: line 35: dpkg-source: command not found
>>
>> I'm not sure what happened because I was able to create the tarball from 
>> the previous git just fine...  Any idea?
>
> I did some changes to the maintainer scripts a while back... I forget 
> when,
> but now it is a multi-step process.  git-extract.sh extracts a clean
> tree from a git repo.  tar-prepare.sh does all the steps needed to
> generate the documentation, etc.  And tar-create.sh creates the release
> tar.bz2 and the debian orig.tar.gz source package.
>
> I suppose for convenience, I should split that into tar-create.sh and
> deb-src-create.sh :-)  (time passes)  Ok, I did that, and updated git.

Excellent.

> Take a look at the snapshot.sh script in the scripts branch of the git 
> repo
> for the sequence in action.
>

Will do.  I'm on my way to Virginia right now to go house hunting for 10 
days so I don't have access to my Desktop, where I have Fedora installed.  I 
will try the newest git when I get back and we'll see what happens!

>
>> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac 
>> and
>> libtoolize: rerunning libtoolize, to keep the correct libtool macros 
>> in-tree.
>> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
>> libtoolize: putting macros in `../m4'.
>
> Interesting.  I've added these to the root configure.ac and the root
> Makefile.am.  Let me know if this makes it any better for you.

Thanks, I'll keep you posted!

Chris 


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to