> Cool... the ebuild must be git aware.
>
9999 ebuild are live ebuilds, as in they follow whatever source control
system you need them too
I wish I could see the ebuild. I'm curious about its "libtoolize" step.
> Does it just call ./buildgen.sh from the source, or does it do its own
> thing?
the ebuild is online at http://bugs.gentoo.org/show_bug.cgi?id=215399
> Applying barry-9999-gcc43.patch ... ok
>
> I'm curious what this patch is... is it still needed with the latest git?
> I'm able to build cleanly on a variety of systems, but if this patch fixes
> a build error, I'd like to see it and perhaps include it in upstream.
It adds various includes to a few files, i just compiled without errors
without this patch
> Applying barry-9999-tarfile-int.patch ... ok
>
> If this is the patch I think it is, it is a bug in Gentoo's version of
> libtar
> and is well documented on this list. It shouldn't affect your build, but
> if you care about Gentoo being accurate, you might want to submit a bug
> report. I'm happy to provide additional details if you need them.
This fixes errors in tarfile-opts-nt.cc:
tarfile-ops-nt.cc:108: error: invalid conversion from âint (*)(int)â to
âint (*)(long int)â
tarfile-ops-nt.cc:108: error: invalid conversion from âssize_t (*)(int,
void*, size_t)â to âssize_t (*)(long int, void*, size_t)â
tarfile-ops-nt.cc:108: error: invalid conversion from âssize_t (*)(int,
const void*, size_t)â to âssize_t (*)(long int, const void*, size_t)â
Additional details would be great on this.
> configure: running /bin/sh ./configure --disable-option-checking
> '--prefix=/usr' '--host=x86_64-pc-linux-gnu' '--mandir=/usr/share/man'
> '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc'
> '--localstatedir=/var/lib' '--libdir=/usr/lib64'
> '--with-boost==/usr/include' '--enable-gui' '--with-libtar==/usr/lib'
> '--with-libz==/usr/lib' '--enable-opensync-plugin'
> '--build=x86_64-pc-linux-gnu' 'build_alias=x86_64-pc-linux-gnu'
> 'host_alias=x86_64-pc-linux-gnu' 'CFLAGS=-march=native -O2'
> 'LDFLAGS=-Wl,--hash-style=both' 'CXXFLAGS=-march=native -O2'
> --cache-file=/dev/null --srcdir=.
>
>
> After the configure step, there will be a file called 'config.log' that
> will be generated by the configure script. This is the log I was asking
> for, but the above configure command line hints at the problem I was
> suspecting.
>
> Somehow, configure is getting called with multiple equal signs:
>
--with-libtar==/usr/lib
> --with-libz==/usr/lib
> --with-boost==/usr/include
> Comparing with the error from your original email:
>
> > /bin/sh ../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++
> > -D__BARRY_BOOST_MODE__ -D_REENTRANT -I=/usr/include/include -ansi -Wall
> > -g -march=native -O2 -L=/usr/include/lib -Wl,--hash-style=both -o btool
> > btool-btool.o ../src/libbarry.la -lusb -lpthread -lboost_serialization
> > -lpthread
> > mv -f .deps/bs11nread-bs11nread.Tpo .deps/bs11nread-bs11nread.Po
> > ../libtool: line 4999: cd: =/usr/include/lib: No such file or directory
> > libtool: link: cannot determine absolute directory name of
> > `=/usr/include/lib'
>
> That equals sign is confusing libtool.
Ok, sorry about that, I just removed it. This should not be an issue
anymore.
Nils
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
