Somebody claiming to be Stephen Paul Weber wrote:
Somebody claiming to be Duncan Coutts wrote:
On 8 December 2012 20:36, Stephen Paul Weber wrote:
The ./Setup program is passing the selected gcc to hsc2hs, so if you
want to use a different gcc, then use --with-gcc=whatever, and then
./Setup wil
Somebody claiming to be Duncan Coutts wrote:
On 8 December 2012 20:36, Stephen Paul Weber wrote:
The ./Setup program is passing the selected gcc to hsc2hs, so if you
want to use a different gcc, then use --with-gcc=whatever, and then
./Setup will also pass that on to hsc2hs.
This seems likely
On 8 December 2012 20:36, Stephen Paul Weber wrote:
> For some reason after
>
> ./Setup configure --configure-option=--target=i486-pc-nto-qnx8.0.0
> --configure-option=--build=i686-linux-gnu
> --configure-option=--host=i686-linux-gnu --hsc2hs-option=--cross-safe
> --hsc2hs-option=--cross-compile -
For some reason after
./Setup configure --configure-option=--target=i486-pc-nto-qnx8.0.0
--configure-option=--build=i686-linux-gnu
--configure-option=--host=i686-linux-gnu --hsc2hs-option=--cross-safe
--hsc2hs-option=--cross-compile --hsc2hs-option=--cc=qcc
run on the network library (with m
