Re: [Sablevm-developer] actual build failure not catched (sablevm-nativelib build dep on sablevm-nativelib)

[Grzegorz P. <gr...@se...>]

W li=B6cie z =B6ro, 11-09-2002, godz. 22:53, Grzegorz Prokopski pisze:=20
> Hi!
>=20
> I reported previously, that from sablevm-nativelib source some of the
> libs are not build sometimes. So I made two builds - one w/o
> old sablevm-native installed, one - with. And compared build
> outputs. Here's what I found:
[...]
> 2. Some neat trick like LD_LIBRARY_PATH set to directory w/ just builded
> libclasspath should be used (I'll try it in a minute) (btw. is it
> portable outside Linux/glibc? no I think)
> Maybe -L parameter usage would be wiser? Surely.
LD_LIBRARY_PATH tric didn't worked
I don't know autotools well enough (yet? ;-) to fix this myself.
They're just too auto-matic for me :-/

> Current situtation is that I need to have sablevm-nativelib installed=20
> to be able build new sablevm-nativelib which is unnacceptable.
Anyway I uploaded 1.0.4 version to unstable. sablevm went to queue/NEW
of course and will have to be processed by ftpmasters (hopefully).

Because of above bug sablevm-nativelib won't be properly build
by autobuilders, as it now build-depends on itself (it's sick, I told
you). The i386 version hovewer worked for me fully.

> PS: The problem with sablevm-n.e.w looking for libs in o.l.d versions
> if those o.l.d versions were installed during the build - seems to be
> on similar ground. It seem that sablevm checks in /usr/lib,
> /usr/lib/sablevm for versions first, instead of own build directories.
> ATM I need to build conflict w/ sablevm and build depend on
> libsablevm-native with specified version that coresponds to sablevm
> version.
I just added build-conflicts: sablevm to sablevm control file and it
seems to solve the issue, even if I'd rather call it a workaround.

Regards

						GBP