Christopher Tarricone wrote:
> On Fri, Dec 14, 2007 at 06:58:31PM -0500, Paul Dugas wrote:
> > New laptop arrived a couple weeks ago and I've been getting things in
> > line steadily. Got to barry last night and ran into a hitch. Slept on
> > it but still got the issue.
>
> Thanks for testing on 64bit. I haven't tested the sync module on
> 64 bit platforms, so it is a bit of an unknown. Please don't take my
> delay in answering as disinterest... I'm very interested in getting
> Barry working on multiple platforms.
>
>
> > > ...
> > > Processing files: barry-debuginfo-0.11-1
> > > Provides: barry_sync.so.debug()(64bit)
> libbarry.so.0.0.11.debug()(64bit)
> > > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> > > Requires: barry_sync.so()(64bit) libbarry.so.0()(64bit)
> > > Checking for unpackaged file(s): /usr/lib/rpm/check-files
> /var/tmp/barry-1-0.11-root
> > > error: Installed (but unpackaged) file(s) found:
> > > /usr/lib/opensync/plugins/barry_sync.la
> > > /usr/lib/opensync/plugins/barry_sync.so
> > >
> > >
> > > RPM build errors:
> > > File not found by glob:
> /var/tmp/barry-1-0.11-root/usr/lib64/opensync/plugins/*
> > > Installed (but unpackaged) file(s) found:
> > > /usr/lib/opensync/plugins/barry_sync.la
> > > /usr/lib/opensync/plugins/barry_sync.so
> >
> > It's looking in lib64 for the plugins installed under lib. The
> > libopensync-0.22 package created the lib64 directory and that's where
> > the evo2_sync.so plugin is. The autoconf config under opensync-plugin
> > is running $(pkg-config --variable=plugindir opensync-1.0) to define
> > OPENSYNC_PLUGINDIR which results in /usr/lib64/opensync/plugins. The
> > Makefile.am down in src/ appears to be using that properly. I'm
> > confused.
> >
> > Any thoughts on how to get around this?
>
> The only thing I can think of is that perhaps the 64bit rpmbuild process
> is running configure or make differently than on 32bit.
>
> Could you send me the build log from the following command:
> rpmbuild -vv -ba barry.spec --with opensync > log 2>&1
>
> This can be hacked around, by moving the plugin files after the install,
> but I'd like to see the whole process. Maybe there is something I'm
> missing.
>
> Thanks,
> - Chris
>
>
>
> Thread View
>
> Thread Author Date
> [Barry-devel] RPM trouble with 0.11 on F8 x86_64 Paul Dugas
> <[EMAIL PROTECTED]> Re: [Barry-devel] RPM trouble with 0.11 on F8
> x86_64
> From: Chris Frey <[EMAIL PROTECTED]> - 2007-12-21 21:39
> On Fri, Dec 14, 2007 at 06:58:31PM -0500, Paul Dugas wrote:
> > New laptop arrived a couple weeks ago and I've been getting things in
> > line steadily. Got to barry last night and ran into a hitch. Slept on
> > it but still got the issue.
>
> Thanks for testing on 64bit. I haven't tested the sync module on
> 64 bit platforms, so it is a bit of an unknown. Please don't take my
> delay in answering as disinterest... I'm very interested in getting
> Barry working on multiple platforms.
>
>
> > > ...
> > > Processing files: barry-debuginfo-0.11-1
> > > Provides: barry_sync.so.debug()(64bit)
> libbarry.so.0.0.11.debug()(64bit)
> > > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> > > Requires: barry_sync.so()(64bit) libbarry.so.0()(64bit)
> > > Checking for unpackaged file(s): /usr/lib/rpm/check-files
> /var/tmp/barry-1-0.11-root
> > > error: Installed (but unpackaged) file(s) found:
> > > /usr/lib/opensync/plugins/barry_sync.la
> > > /usr/lib/opensync/plugins/barry_sync.so
> > >
> > >
> > > RPM build errors:
> > > File not found by glob:
> /var/tmp/barry-1-0.11-root/usr/lib64/opensync/plugins/*
> > > Installed (but unpackaged) file(s) found:
> > > /usr/lib/opensync/plugins/barry_sync.la
> > > /usr/lib/opensync/plugins/barry_sync.so
> >
> > It's looking in lib64 for the plugins installed under lib. The
> > libopensync-0.22 package created the lib64 directory and that's where
> > the evo2_sync.so plugin is. The autoconf config under opensync-plugin
> > is running $(pkg-config --variable=plugindir opensync-1.0) to define
> > OPENSYNC_PLUGINDIR which results in /usr/lib64/opensync/plugins. The
> > Makefile.am down in src/ appears to be using that properly. I'm
> > confused.
> >
> > Any thoughts on how to get around this?
>
> The only thing I can think of is that perhaps the 64bit rpmbuild process
> is running configure or make differently than on 32bit.
>
> Could you send me the build log from the following command:
> rpmbuild -vv -ba barry.spec --with opensync > log 2>&1
>
> This can be hacked around, by moving the plugin files after the install,
> but I'd like to see the whole process. Maybe there is something I'm
> missing.
>
> Thanks,
> - Chris
>
> Re: [Barry-devel] RPM trouble with 0.11 on F8 x86_64
> From: Nathan <[EMAIL PROTECTED]> - 2007-12-22 00:23
>
> Attachments: Message as HTML On Fri, 2007-12-21 at 16:39 -0500,
> Chris Frey wrote:
> > On Fri, Dec 14, 2007 at 06:58:31PM -0500, Paul Dugas wrote:
> > > New laptop arrived a couple weeks ago and I've been getting things in
> > > line steadily. Got to barry last night and ran into a hitch. Slept on
> > > it but still got the issue.
> >=20
> > Thanks for testing on 64bit. I haven't tested the sync module on
> > 64 bit platforms, so it is a bit of an unknown. Please don't take my
> > delay in answering as disinterest... I'm very interested in getting
> > Barry working on multiple platforms.
>
> FYI, I have barry 0.10.0 working on 64-bit, The opensync plugin works
> too except for the evolution plugin, not barry's. I haven't had a
> chance to sit down and debug it. So it should work once I got that
> working. I am on ubuntu though so it might be different with F8.
>
>
> >=20
> > > > ...
> > > > Processing files: barry-debuginfo-0.11-1
> > > > Provides: barry_sync.so.debug()(64bit)
> libbarry.so.0.0.11.debug()(64b=
> it)
> > > > Requires(rpmlib): rpmlib(CompressedFileNames) <=3D 3.0.4-1
> rpmlib(Pay=
> loadFilesHavePrefix) <=3D 4.0-1
> > > > Requires: barry_sync.so()(64bit) libbarry.so.0()(64bit)
> > > > Checking for unpackaged file(s): /usr/lib/rpm/check-files
> /var/tmp/ba=
> rry-1-0.11-root
> > > > error: Installed (but unpackaged) file(s) found:
> > > > /usr/lib/opensync/plugins/barry_sync.la
> > > > /usr/lib/opensync/plugins/barry_sync.so
> > > >=20
> > > >=20
> > > > RPM build errors:
> > > > File not found by glob: /var/tmp/barry-1-0.11-root/usr/lib64/open=
> sync/plugins/*
> > > > Installed (but unpackaged) file(s) found:
> > > > /usr/lib/opensync/plugins/barry_sync.la
> > > > /usr/lib/opensync/plugins/barry_sync.so
> > >=20
> > > It's looking in lib64 for the plugins installed under lib. The
> > > libopensync-0.22 package created the lib64 directory and that's where
> > > the evo2_sync.so plugin is. The autoconf config under opensync-plugin
> > > is running $(pkg-config --variable=3Dplugindir opensync-1.0) to
> define
> > > OPENSYNC_PLUGINDIR which results in /usr/lib64/opensync/plugins. The
> > > Makefile.am down in src/ appears to be using that properly. I'm
> > > confused.=20
> > >=20
> > > Any thoughts on how to get around this?
> >=20
> > The only thing I can think of is that perhaps the 64bit rpmbuild
> process
> > is running configure or make differently than on 32bit.
> >=20
> > Could you send me the build log from the following command:
> > rpmbuild -vv -ba barry.spec --with opensync > log 2>&1
> >=20
> > This can be hacked around, by moving the plugin files after the
> install,
> > but I'd like to see the whole process. Maybe there is something I'm
> > missing.
>
> You could probably get a round by changing the OPENSYNC_PLUGINDIR in the
> spec file so it is pointing to the right place.
>
> Nathan
>
>
>
I do not know if this issue was resolved or not but it I am having the
same issue. My build fails with the following:
+ /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
* to fail. To ignore these errors, you can set the '$QA_RPATHS'
* environment variable which is a bitmask allowing the values
* below. The current value of QA_RPATHS is 0x0000.
*
* 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
* issue but are introducing redundant searchpaths without
* providing a benefit. They can also cause errors in multilib
* environments.
* 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
* nor relative filenames and can therefore be a SECURITY risk
* 0x0004 ... insecure RPATHs; these are relative RPATHs which are a
* SECURITY risk
* 0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
* RPATHs; this is just a minor issue but usually unwanted
* 0x0010 ... the RPATH is empty; there is no reason for such RPATHs
* and they cause unneeded work while loading libraries
* 0x0020 ... an RPATH references '..' of an absolute path; this will
break
* the functionality when the path before '..' is a symlink
*
*
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
* $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute
check-rpaths like
* $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
*
*******************************************************************************
ERROR 0001: file '/usr/lib/opensync/plugins/barry_sync.so' contains a
standard rpath '/usr/lib64' in [/usr/lib64]
ERROR 0001: file '/usr/bin/upldif' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
ERROR 0001: file '/usr/bin/btool' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
ERROR 0001: file '/usr/bin/bktrans' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
ERROR 0001: file '/usr/bin/bidentify' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
ERROR 0001: file '/usr/sbin/pppob' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
error: Bad exit status from /var/tmp/rpm-tmp.45831 (%install)
If I then run:
QA_RPATHS=$[ 0x0001 ] rpmbuild -vv -ba barry.spec --with opensync
I then get the same erRPM build errors:
File not found by glob:
/var/tmp/barry-1-0.11-root/usr/lib64/opensync/plugins/*
Installed (but unpackaged) file(s) found:
/usr/lib/opensync/plugins/barry_sync.la
/usr/lib/opensync/plugins/barry_sync.so
in the file
/home/chris/rpmbuild/BUILD/barry-0.11/opensync-plugin/config.log the
following configure command was issued:
$ ./configure --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu
--program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin
--sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share
--includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec
--localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man
--infodir=/usr/share/info PKG_CONFIG_PATH=..: CXXFLAGS=-I../..
LDFLAGS=-L../../src
But it seems that the plugins still wish to go to /usr/lib instead of
/usr/lib64
Any ideas?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Barry-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/barry-devel
