From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Compiled programs fail to run from Cygwin Terminal, but work from windows cmd
Date: Mon, 26 Jun 2017 14:16:00 -0000 [thread overview]
Message-ID: <83b613d9-03ec-64e4-2e4c-32f312ce73a2@gmail.com> (raw)
In-Reply-To: <CANZ2p_c7k5w766knwM0BVhsxu7rZvKdTKwT+3DZ-H2ZtXH0q0Q@mail.gmail.com>
On 6/22/2017 11:57 AM, Wouter van Doorn wrote:
>>
>> Is your prompt overwriting the output of the program?
>>
>> Try:
>>
>> $ hello | cat
>> $ hello | grep ello
>>
>> etc.
>
> On 22 June 2017 at 14:57, cyg Simple <cygsimple@gmail.com> wrote:
> Nice thought, but no, that's not it. The standard utilities behave
> normally, only the things I compile myself stay schtumm.
>
I've not seen you explain your compile and link process; assuming is a
bad idea. I've not seen any attachments as per the problems link in
every email in this thread. What is the output of uname -a, gcc -v and
ld -v?
--
cyg Simple
--
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
next prev parent reply other threads:[~2017-06-26 14:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 21:10 Wouter van Doorn
2017-06-21 21:49 ` René Berber
2017-06-22 13:13 ` Wouter van Doorn
2017-06-22 13:57 ` cyg Simple
2017-06-22 15:57 ` Wouter van Doorn
2017-06-26 14:16 ` cyg Simple [this message]
2017-06-26 18:51 ` Wouter van Doorn
2017-06-22 14:09 ` René Berber
2017-06-22 16:01 ` Wouter van Doorn
2017-06-22 16:19 ` René Berber
2017-06-22 19:11 ` Wouter van Doorn
2017-06-22 17:46 ` Soegtrop, Michael
2017-06-23 0:50 ` Andrey Repin
2017-06-23 19:30 ` Wouter van Doorn
2017-06-22 22:33 ` Thomas Wolff
2017-06-25 6:16 ` Wouter van Doorn
2017-06-25 6:23 ` René Berber
2017-06-25 6:32 ` Wouter van Doorn
2017-06-25 16:04 ` Brian Inglis
2017-06-25 8:33 ` Achim Gratz
2017-06-25 8:50 ` Houder
2017-06-26 19:01 ` Wouter van Doorn
2017-06-27 7:26 ` Wouter van Doorn
2017-06-27 8:14 ` Soegtrop, Michael
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=83b613d9-03ec-64e4-2e4c-32f312ce73a2@gmail.com \
--to=cygsimple@gmail.com \
--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).