Wgcc 2.0 RC2 released.

wgcc is a cross-compiler tool primarily written for Microsoft's Interix. Its primary purpose is to produce native Windows binaries (internally using the Microsoft Tool chain), and to mimic the behaviour of the GNU compiler collection. This means that wgcc understands many of GCC's command line argu

Re: deploying libraries and executables from a staging area

* Noel Yap wrote on Thu, Sep 21, 2006 at 05:40:12PM CEST: > On 9/21/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > >3) For any library in (1) and (2): are they libtool libraries? If yes, > >please post the *.la file. In any case (libtool libs or not), please > >post `objdump -p libfoo.so' fo

Re: deploying libraries and executables from a staging area

On 9/21/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Thanks for the detailed definitions and notes. They help a lot. Now, please answer the crucial missing questions: 1) Does the stuff (programs and libraries) you are building in your package depend upon installed libraries that are not y

Re: AC_LIBTOOL_SYS_DYNAMIC_LINKER "gcc -print-search-dirs" problem

On Sep 21, 2006, at 5:43 AM, Kate Minola wrote: Comments? Suggestions for improvement? Hi Kate, I'm hoping to have a chance to look at this again at the weekend, however, as Ralf sent me off to read autoconf's limitations of the usual tools, I amsending you off there too :(

Re: deploying libraries and executables from a staging area

* Noel Yap wrote on Wed, Sep 20, 2006 at 11:43:58PM CEST: > On 9/20/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > >To be able to say more (including whether it works portably ATM or not), > >we need to know > >- which libraries are involved (uninstalled ones, installed but at a > > different