On Wed, Feb 25, 2009 at 10:40:49PM -0500, Marc R. O'Connor wrote:
> Attached is the entire log of the installation for barry(Gentoo using
> paludis)
Hi Marc,
Thanks for the log. Some comments below...
> Starting builtin_loadenv
> Done builtin_loadenv
> Starting src_unpack
> git update start -->
> repository: git://repo.or.cz/barry.git
> local clone: /var/paludis/distfiles/git-src/barry
> committish: master
> >>> Unpacked to /var/tmp/paludis/app-pda-barry-9999/work/barry-9999
Cool... the ebuild must be git aware.
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtoolize: You should add the contents of the following files to
> `aclocal.m4':
[snip]
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?
It might be worth comparing.
> 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.
> 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.
> econf: updating
> /var/tmp/paludis/app-pda-barry-9999/work/barry-9999/config.guess with
> /usr/share/gnuconfig/config.guess
> econf: updating
> /var/tmp/paludis/app-pda-barry-9999/work/barry-9999/config.sub with
> /usr/share/gnuconfig/config.sub
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking for C compiler default output file name... a.out
[configure snipped]
> 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.
> /bin/sh ../libtool --tag=CXX --mode=link x86_64-pc-linux-gnu-g++
> -D_REENTRANT -I=/usr/include/include -ansi -Wall -g -march=native -O2
> -L=/usr/include/lib -Wl,--hash-style=both -o bs11nread bs11nread-bs11nread.o
> ../src/libbarry.la -lusb -lpthread -lboost_serialization -lpthread
> mv -f .deps/btool-btool.Tpo .deps/btool-btool.Po
> make[2]: Leaving directory
> `/var/tmp/paludis/app-pda-barry-9999/work/barry-9999/tools'
> make[1]: Leaving directory
> `/var/tmp/paludis/app-pda-barry-9999/work/barry-9999'
>
> Install error:
> * In program paludis -i barry:
> * When performing install action from command line:
> * When executing install task:
> * When installing 'app-pda/barry-9999:0::local':
> * When running an ebuild command on 'app-pda/barry-9999:0::local':
> * Install error: Install failed for 'app-pda/barry-9999:0::local'
Oddly, that previous error is not listed here. Maybe it is in some
log generated by paludis?
> This E-mail, including any attachments, may be intended solely for the
> personal
> and confidential use of the sender and recipient(s) named above. This message
> may include advisory, consultative and/or deliberative material and, as such,
> would be privileged and confidential and not a public document. Any
> Information
> in this e-mail identifying a client of the Department of Human Services is
> confidential. If you have received this e-mail in error, you must not review,
> transmit, convert to hard copy, copy, use or disseminate this e-mail or any
> attachments to it and you must delete this message. You are requested to
> notify
> the sender by return e-mail.
This is an open source project. You are welcome to participate, but please
don't post to the list if you don't have permission to. We can't be
responsible for what you post, so your disclaimer is meaningless.
- Chris
------------------------------------------------------------------------------
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
