public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Philipp Wiesner <philipp.wiesner83@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-autoconf@gnu.org, crossgcc@sourceware.org
Subject: Re: autoconf: ./configure fails on cygwin for crosstool-ng-1.24.0
Date: Mon, 06 May 2019 22:09:00 -0000	[thread overview]
Message-ID: <2505a67f-07a3-4e70-2132-bf33b8ec1c91@gmail.com> (raw)
In-Reply-To: <c628477c-4e80-09b3-1b46-3eca1d4f8541@cs.ucla.edu>

Hello Paul,
hello Allan,

thanks to your input I was sure that the problem had to be found in my 
specific configuration and so I looked around and found it:
I had installed cygwin into the windows program folder and symlinked the 
folder to C:\cygwin64. This seems to have caused problems, because 
deleting the symlink and moving the folder to C:\cygwin64 directly 
resolved the issue. Now ./configure runs until it fails to find libtool, 
which I consider a success.

I can provide the /bin/bash -x ./configure log file upon request.

Thank you!

Philipp

Am 06.05.2019 um 23:19 schrieb Paul Eggert:
> It should work with your Bash. The fact that it fails with both your
> Bash, and with recent zsh, suggest a configuration problem of some sort
> (not a problem with your shells per se). You can try debugging it by
> using 'bash -x configure', or by putting 'set -x' into 'configure' just
> before the place you think is causing the problem.
>

      reply	other threads:[~2019-05-06 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1f2e0707-6563-36a3-8e1e-1768bee278eb@gmx.de>
2019-05-06 20:14 ` Fwd: " Philipp
     [not found]   ` <CABwpfdT-f=vWCOgMU=mfsOXKP3kNRMa=7VL7GjBAy4d1vR5NDw@mail.gmail.com>
2019-05-06 21:02     ` Philipp
2019-05-06 21:19 ` Paul Eggert
2019-05-06 22:09   ` Philipp Wiesner [this message]

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=2505a67f-07a3-4e70-2132-bf33b8ec1c91@gmail.com \
    --to=philipp.wiesner83@gmail.com \
    --cc=bug-autoconf@gnu.org \
    --cc=crossgcc@sourceware.org \
    --cc=eggert@cs.ucla.edu \
    /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).