public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: Robert Collins <robert.collins@syncretize.net>
Cc: Dylan Cuthbert <dylan@q-games.com>, cygwin@cygwin.com
Subject: Re: g++ (v.3.1.1-4)  -mno-cygwin with a hello world sample crashes oddly
Date: Sun, 21 Jul 2002 11:53:00 -0000	[thread overview]
Message-ID: <7330147559.20020721164007@familiehaase.de> (raw)
In-Reply-To: <1027256463.7101.23.camel@lifelesswks>

Hallo Robert,

Am Sonntag, 21. Juli 2002 um 15:01 schriebst du:

> On Sun, 2002-07-21 at 22:55, Robert Collins wrote:
>> On Sun, 2002-07-21 at 22:56, Dylan Cuthbert wrote:
>> > That's very odd behaviour!  What else is in your current directory?  Is
>> > there a hiho.exe.exe?  :-)

No, I got 'hiho' after compiling with '-o hiho', after moving this to
'hiho.exe' I got the error.

>> I see the same quirks on linux. Something strange here.

> Ah, I was trying to run it on a nonexec partition (long story).

I have some of these too... how do I know if the partitions are
nonexec or not?  No hint when I type in 'mount'.  I would like to
see a trigger in setup.exe to decide whether I want to have a shared
drive to be exec or nonexec.

> Works fine for me(tm).


-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-07-21 14:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-20 18:44 Dylan Cuthbert
2002-07-20 18:57 ` Christopher Faylor
2002-07-20 19:13   ` Jim George
2002-07-20 23:40   ` Dylan Cuthbert
2002-07-21  0:43     ` Robert Collins
2002-07-21  1:52       ` g++ (v.3.1.1-4) -mno-cygwin with a hello world sample crashesoddly Dylan Cuthbert
2002-07-21  2:21         ` Robert Collins
2002-07-22  0:46     ` g++ (v.3.1.1-4) -mno-cygwin with a hello world sample crashes oddly Gary R. Van Sickle
2002-07-21  3:39 ` Gerrit P. Haase
2002-07-21  5:54   ` Sylvain Petreolle
2002-07-21  5:55     ` Sylvain Petreolle
2002-07-21  7:59     ` Gerrit P. Haase
2002-07-21  9:51       ` Sylvain Petreolle
2002-07-21 10:00         ` Dylan Cuthbert
2002-07-21 11:49         ` Gerrit P. Haase
2002-07-21  7:39   ` Dylan Cuthbert
2002-07-21  8:01     ` Gerrit P. Haase
2002-07-21  9:58       ` Dylan Cuthbert
2002-07-21  9:58         ` Robert Collins
2002-07-21 10:48           ` Robert Collins
2002-07-21 11:53             ` Gerrit P. Haase [this message]
2002-07-21 13:12               ` Christopher Faylor
2002-07-21 13:21             ` Christopher Faylor
2002-07-21 18:37               ` Robert Collins
2002-07-21 19:49                 ` Christopher Faylor
2002-07-21 20:09                   ` Robert Collins
2002-07-22  1:39                 ` Gerrit P. Haase
2002-07-21 12:43       ` Randall R Schulz
2002-07-21 13:05         ` Gerrit P. Haase
2002-07-21 13:21         ` Christopher Faylor
2002-07-21 14:58           ` Sylvain Petreolle
2002-07-21 20:33             ` Christopher Faylor
2002-07-22  0:00               ` Dylan Cuthbert
2002-07-21 13:33 news
2002-07-21 19:33 ` Christopher Faylor
2002-07-24 11:07   ` news
     [not found]   ` <E17XOVg-0007UX-00@quimby.gnus.org>
2002-07-25  4:12     ` Dylan Cuthbert

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=7330147559.20020721164007@familiehaase.de \
    --to=gp@familiehaase.de \
    --cc=cygwin@cygwin.com \
    --cc=dylan@q-games.com \
    --cc=robert.collins@syncretize.net \
    /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).