public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [HEADSUP] Moving setup sources to git
Date: Tue, 10 Feb 2015 17:01:00 -0000	[thread overview]
Message-ID: <87a90l8zv6.fsf@Rainer.invalid> (raw)
In-Reply-To: <20150210083104.GD2878@calimero.vinschen.de> (Corinna Vinschen's	message of "Tue, 10 Feb 2015 09:31:04 +0100")

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?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

  parent reply	other threads:[~2015-02-10 17:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 16:24 Corinna Vinschen
2015-02-09 16:50 ` Warren Young
2015-02-09 17:17 ` Achim Gratz
2015-02-09 19:29 ` Achim Gratz
2015-02-09 19:36 ` Frank Fesevur
2015-02-09 19:46   ` Achim Gratz
2015-02-09 20:00     ` Frank Fesevur
2015-02-09 20:21     ` Corinna Vinschen
2015-02-16 18:45       ` Achim Gratz
2015-02-09 20:59     ` Jon TURNEY
2015-02-09 21:48       ` Achim Gratz
2015-02-10  8:31         ` Corinna Vinschen
2015-02-10 13:55           ` Vin Shelton
2015-02-10 14:14             ` Frank Fesevur
2015-02-10 15:22               ` Corinna Vinschen
2015-02-10 17:01           ` Achim Gratz [this message]
2015-02-10 19:47             ` Corinna Vinschen
2015-02-10 18:48 ` David Stacey
2015-02-10 18:53   ` Achim Gratz
2015-02-10 18:56     ` David Stacey
2015-02-10 19:46       ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a90l8zv6.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).