On Jul 8, 2007, at 4:34 PM, Ralf S. Engelschall wrote:
On Sun, Jul 08, 2007, Jeff Johnson wrote:
AFAICT, the core problem preventing populating dependency_libs
is that automake is confused by having two -lz libraries.
Can you be more specific here, Jeff? What particular
error occurs under what particular platform?
Neon needs
system -lz, while everything else is using rpmz_* wrapped symbols.
How about this patch to change internal libz -> librpmz?
But this patch changes a lot more. It actually links again all libs
into more than just librpmmisc. And it uses bad constructs like
"librpmio_la_LDFLAGS += -L$(usrlibdir) -lneon" which is a horribly
system specific thing, etc.
Yep. I had
ifeq($(WITH_FOO),yes)
...
endif
constructs around the added lines, easily added.
AFAICT,
that should allow populating dependency_libs internal to *.la
as before, without reverting what has already been accomplished.
Sorry, it actually _IS_ reverting things and this way especially
breaks
things again.
;-)
Well, I kinda want dependency_libs populated. That's called reversion,
or unreverting feature regression.
Otherwise, please check some configuration into devtool.conf
that I can check. There are way too many configure options for me
to guess what is desired.
The ultimative inverse to your "use 'devtool jbj' under Fedora 7"
usually is to build RPM fully statically and without any third-party
libs installed in any system locations. This way one immediately
can see how things break with "-L$(usrlibdir) -lneon" or similar
constructs. Sorry that I've still not checked in my BUILD.sh script
into
devtool.conf, but it would require to download third-party libs and
build (but not install them) locally (side by side with RPM 5). I'll
look what I can do.
In the meantime please tell me in more detail what particular Automake
problem you are faced with and I'll try hard to resolve it for us in a
way we do not break anything again -- which we already fixed recently.
There are other obvious problems with existing HEAD that prevent
choices between internal/external/none. Forward motion requires
identifying what configurations are usefully needed and insuring
that those configurations are functional.
A full -blown regression on all possible configurations is non-trivial.
I'd like to see exactly what configuration(s) you wish to use in
devtool.conf so that I can tell explicitly what more needs doing.
You already have the configuration that I am trying to use with
./devtool jbj
Meanwhile, automake was adding
-L../zlib -lz
and was refusing to bundle the internal zlib into librpmio until
I renamed libz -> librpmz. So automake et al appears to be use
first found, renaming avoids the issue.
IIRC, you mentioned that internal zlib was misbehaving like 10 days ago,
which was your motivation for creating librpmmisc.
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
