On Feb 10 18:01, Achim Gratz wrote:
> Corinna Vinschen writes:
> > On Feb  9 22:48, Achim Gratz wrote:
> >> At the time of writing an in-tree build configuration did not work for
> >> me, although that later turned out to be an unrelated problem IIRC.  At
> >> the moment I actually build in-tree since you can't configure both
> >> architectures in an out-of-tree build anyway.
> >
> > This.  I don't understand.  Here's what I do:
> 
> Thanks.  I don't understand it either anymore because I just tried this
> again (in a slightly different way because I build for 32bit on 32bit
> and 64bit on 64bit) and it now works.  I'm not sure what went wrong the
> first time I tried it, but it was telling me something about me needing
> to reconfigure and throwing away the cache each time I built for the
> other architecture.
> 
> >   $ bash -c "NOCONFIGURE=1 ./bootstrap.sh"
> 
> Very obvious now... but still too well hidden.
> 
> >   $ cat > conf.sh <<EOF
> >   #!/bin/bash
> >   cpu=$(basename $PWD)
> >   [ -n "$cpu" ] && \
> >     ../setup/configure --host=$cpu-w64-mingw32 --target=$cpu-w64-mingw32
> >   EOF
> 
> That's been bothering me for a while, the test for determining the build
> and host type in bootstrap.sh just doesn't give the right results most
> of the time and I always have to add the --host=<...> manually.  What (if
> anything) is --target=<..> doing?

Some autoconf thingy.  I'm not sure anymore but it could have had to do
with cross building on Linux.  After I created the conf.sh files I'm
working with them and never looked again.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat