public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: juan carlos Rebate <nerus492@gmail.com>
To: Brian.Inglis@systematicsw.ab.ca, cygwin@cygwin.com
Subject: Re: failed configure
Date: Sat, 22 Oct 2016 08:03:00 -0000	[thread overview]
Message-ID: <CAJzZnfQArd0ceXq1c4g4d+D2V82dL80WmGwhYh2MKH2oyAf5gA@mail.gmail.com> (raw)
In-Reply-To: <41a3ffd4-0c4c-0f25-5835-d1f096fc00b2@SystematicSw.ab.ca>

2016-10-20 3:33 GMT+02:00 Brian Inglis <Brian.Inglis@systematicsw.ab.ca>:
> On 2016-10-19 09:09, juan carlos Rebate wrote:
>>
>> 2016-10-19 5:33 GMT+02:00 Brian Inglis <Brian.Inglis@systematicsw.ab.ca>:
>>>
>>> On 2016-10-18 20:10, juan carlos Rebate wrote:
>>>>
>>>> 2016-10-19 3:50 GMT+02:00 Brian Inglis
>>>> <Brian.Inglis@systematicsw.ab.ca>:
>>>>>
>>>>> On 2016-10-18 19:15, juan carlos Rebate wrote:
>>>>>>
>>>>>> 2016-10-19 2:31 GMT+02:00 René Berber <rene.berber@gmail.com>:
>>>>>>>
>>>>>>> On 10/18/2016 7:04 PM, juan carlos Rebate wrote:
>>>>>>>>
>>>>>>>> in the three applications receive the same error
>>>>>>>> error cc either not exit or no work,
>>>>>>>
>>>>>>> First check that gcc is in the path, something like this (in mintty):
>>>>>>> $ which gcc
>>>>>>> /usr/bin/gcc
>>>>>>> $ which cc
>>>>>>> /usr/bin/cc
>>>>>>>>
>>>>>>>> but this is not true, when I call to gcc works correctly, todod
>>>>>>>> tutorials tell me that do the following ./configure --cc=gcc or
>>>>>>>> ./configure --cc="gcc-3 -mno-cygwin" --host-cc=gcc-3
>>>>>>>
>>>>>>> Wrong, useless, tutorials.  What you really do, if needed (and it
>>>>>>> really
>>>>>>> shouldn't be needed, see above).
>>>>>>> ./configure CC=gcc
>>>>>>> In fact you can learn that by simply running:
>>>>>>> ./configure --help
>>>>>
>>>>> On Unix most executables have no extension, so Cygwin does not always
>>>>> show the .exe following a program name, and /usr/bin/gcc is the normal
>>>>> Cygwin output for the compiler gcc.exe, and is not a folder name.
>>>>> If you look for the file under Windows Explorer, you will see the
>>>>> directory entry for gcc.exe, unless you hide extensions.
>>>>> Please run Cygwin using the Cygwin Terminal Start Menu Entry;
>>>>> in that window, cd to the directory where the program configure script
>>>>> was downloaded; run the following command:
>>>>>         ./configure && make
>>>>> without adding any other options, and post the output in a reply here.
>>>>
>>>> jc@DESKTOP-A72U7VL ~/qemu
>>>> $  ./configure && make
>>>> ERROR: "cc" either does not exist or does not work
>>>
>>> Okay you said earlier:
>>>>>>
>>>>>> no on C:\cygwin\usr no gcc folder but if the mingw32 folder, this is
>>>>>> vygwin error because the whole development category is installed
>>>
>>> which implies you installed MinGW, not Cygwin, tools, causing the issue.
>>> You should ask about using these tools on the MinGW mailing list, see:
>>> https://sourceforge.net/p/mingw/mailman/mingw-users/
>>> after reading and following:
>>> http://www.mingw.org/wiki/Getting_Started
>>> http://www.mingw.org/wiki/HOWTO_Install_the_MinGW_GCC_Compiler_Suite
>>> http://www.mingw.org/wiki/MinGW_for_First_Time_Users_HOWTO
>>
>> I do not understand what I said, I said that from the installation
>> graphical cygwin instaé entire category development to avoid
>> dependency problems, was cygwin who installed mingw instead of gcc so
>> that nueevo indicate that failure cygwin
>
>
> If you *successfully* installed the entire Cygwin Base + Development
> categories, you would at least have gcc and cc symlinked to gcc available.
> Whether you would be able to run anything without address space
> exhaustion would be the likely issue.
> Please check Cygwin /var/log/setup.log.full to see if errors were
> reported during installation - attach the log in a reply if so.
>
> Else please follow the Cygwin problem reporting guidelines and attach
> the output from running cygcheck -svr > cygcheck.txt to a reply post.
>
> --
> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
I discovered that this is an error file set for qemu, .configure not
recognize the path of gcc on cygwin, I do not abut how to type in the
path, but I have found that when cygwin installed gcc is installed but
not install g ++ eventhough be releccionado
excuse my bad English, I have 30 years and not have education Anglo
because the Spanish education system is very bad

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2016-10-21 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19  0:32 falled compilations juan carlos Rebate
2016-10-19  1:15 ` René Berber
2016-10-19  1:50   ` juan carlos Rebate
2016-10-19  2:10     ` Brian Inglis
2016-10-19  3:37       ` juan carlos Rebate
2016-10-19  3:37         ` Brian Inglis
2016-10-19 11:11         ` Brian Inglis
2016-10-19 15:30           ` juan carlos Rebate
2016-10-20  4:53             ` failed configure Brian Inglis
2016-10-22  8:03               ` juan carlos Rebate [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=CAJzZnfQArd0ceXq1c4g4d+D2V82dL80WmGwhYh2MKH2oyAf5gA@mail.gmail.com \
    --to=nerus492@gmail.com \
    --cc=Brian.Inglis@systematicsw.ab.ca \
    --cc=cygwin@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).