Re: compiler

[Stuart Anderson <anderson@metrolink.com>]

Erik,
	I had the same thing in mind. lsbcc can actually be a script that
calls the correct compiler for LSB as well as reset include path, define/
undefine any symbols (__LSB__ ??), etc. In recent work with a cross env, it
was similarly useful to have cc, ld, ar and some of the bin utils wrapped in
scripts also. We might want to consider something similar if there turns out
to be a useful reason.


On Tue, 6 Oct 1998, Erik Troan wrote:

> 
> I'd like to jump ahead a little bit.
> 
> It's pretty much given that:
> 
> 	1) LSB programs will need to be linked against some library
> 	2) LSB programs will need to be built with some compiler and linker
> 
> As distributions will probably want to ship an LSB build environment for
> creating highly-portable applications aloing with a build environment
> for linking against the latest, LSB-unapproved libraries, we'll need two
> build environments on many distributions.
> 
> I'd like to propse that building LSB-compliant applications be done with
> 'lsbcc' as the compile/link command. Distributions that want to ship
> a single build environment can just 'ln -s egcs lsbcc' (or whatever) and
> be done with it, while this provides a unified method of building lsb-compliant
> binaries on any distribution.
> 
> Thoughts?
> 
> Erik


                                Stuart

Stuart R. Anderson                               anderson@metrolink.com

Metro Link Incorporated                          South Carolina Office
4711 North Powerline Road                        105 Fox Ridge Run
Fort Lauderdale, Florida 33309                   Lexington, SC 29072
voice: 954.938.0283                              voice: 803.951.3630
fax:   954.938.1982                              SkyTel: 800.405.3401
http://www.metrolink.com/