On Mar 1, 2011, at 2:45 PM, Jeff Johnson wrote:
On Mar 1, 2011, at 2:33 PM, Mark Hatle wrote:
On 3/1/11 1:27 PM, Jeff Johnson wrote:
On Mar 1, 2011, at 2:20 PM, Mark Hatle wrote:
I think jbj might have figured out the problem. Zypper is not using
pcre, but
is instead
On Mar 3, 2011, at 7:09 AM, Qing He wrote:
The only way that backtrace can happen (that I can see) is if RPM, not
zypper, is mis-compiled
using an unfixed (to redefine colliding symbols) system: PCRE with
#include pcreposix.h
which leaves you two choices:
1) fix you system
The following patch was sent to the oe-core mailing list. This fixes a problem
when RPM5 (5.4.0) is linked on an Ubuntu 11.04-alpha host.
--Mark
Original Message
Subject: [OE-core] [PATCHv4 6/6] rpm: Fix linking error encountered in
rpm-native
Date: Thu, 3 Mar 2011 08:09:06
Hmmm ... I'l try, but I'll bet that both
beecrypt and syck are external in this bug report.
Which is kinda pointless since ...
afaik: nothing but rpm uses beecrypt, and anything using syck is
better off with libyaml.
So its m00t whether internal - external (and the rpm tarball ships
with both
This SHOULD be coming through LIBS set by AUtoFu.
The problem with your check-in is that it doesn't
honor LIBS on non-linux (but is otherwise fine).
hth
73 de Jeff
On Mar 3, 2011, at 2:33 PM, Per Øyvind Karlsen wrote:
RPM Package Manager, CVS Repository
http://rpm5.org/cvs/
On 3/3/11 1:44 PM, Jeff Johnson wrote:
Hmmm ... I'l try, but I'll bet that both
beecrypt and syck are external in this bug report.
They shouldn't be. The issue is something to do with stricter library link
checking on newer systems. I.e. if you simply link to librpmio.so you get a
link error,
On Mar 3, 2011, at 2:54 PM, Mark Hatle wrote:
On 3/3/11 1:44 PM, Jeff Johnson wrote:
Hmmm ... I'l try, but I'll bet that both
beecrypt and syck are external in this bug report.
(See above, it's internal)
If its internal, then BeeCrypt/syck are in -lrpmmisc and
the fix needs to be spun
On 3/3/11 2:00 PM, Jeff Johnson wrote:
On Mar 3, 2011, at 2:54 PM, Mark Hatle wrote:
On 3/3/11 1:44 PM, Jeff Johnson wrote:
Hmmm ... I'l try, but I'll bet that both
beecrypt and syck are external in this bug report.
(See above, it's internal)
If its internal, then BeeCrypt/syck are
On Mar 3, 2011, at 3:09 PM, Mark Hatle wrote:
On 3/3/11 2:00 PM, Jeff Johnson wrote:
On Mar 3, 2011, at 2:54 PM, Mark Hatle wrote:
On 3/3/11 1:44 PM, Jeff Johnson wrote:
Hmmm ... I'l try, but I'll bet that both
beecrypt and syck are external in this bug report.
(See above, it's
