RE: [Lsb-build] Need an lsb chroot build environment with real libsinstead of stubs.

> I'd like to set up an LSB chroot build environment for all my 
> packages. 
> There's a slight problem with the lsbdev-chroot solution.  In 
> my RPM build, 
> I compile a tool, then execute the tool within the RPM build. 
>  Since lsbdev-chroot
> only gives me access to stub libraries.  I can't execute the tool.  
> 
> It seems to me that what I need is LSB-si + build tools.  
> This way I would have 
> real libraries instead of stubs, so I can execute my newly 
> compiled tool within
> the RPM build. 
> 
> I can take LSB-si and lsbdev-chroot and start to build such 
> an environment. 
> I'm sending this email to see if anyone else has already done 
> this and can give me some advice. 

There's some work afoot to add build tools to the lsbsi.
I've added the lsb-impl list to this thread for that reason.

Is there a good reason why the alternative build toolkit
(lsbcc) doesn't work for you?  It was designed for the
situation where more tools are needed than are provided
by the chroot, in particulat the GNU-configure type
arrangement where lots of things that aren't part of the
LSB need to run before the build can actually proceed.

Actually more feedback on what would make the chroot more
useful would be appreciated... you've begun that process 
already, thanks.  What libraries are you using that are
not found at run-time?  The lsb stub libraries are still
only pulled in at link time, and the ordinary versions /ought/
to be available at runtime. If not, the existing tools 
(gcc, etc) wouldn't be working either!  If there are only a 
few extra libs needed, you can import them into the chroot via
the config file, or arrange to link those libraries statically.

Anyway, that's the scheme :-)

More details please?