Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: RE: cygwin 1.3.13, gcc 3.2 (no output) and gcc 2.95-3 (output but no permission to execute) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" content-class: urn:content-classes:message Date: Wed, 23 Oct 2002 17:19:31 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Harig, Mark A." To: "Willis, Matthew" , Note-from-DJ: This may be spam Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g9NLJde11823 Also, run a sanity check to make sure that you are running the cygwin and gcc versions that you think are running. $ uname -r $ gcc --version > -----Original Message----- > From: Willis, Matthew [mailto:Matthew.Willis@CIBC.ca] > Sent: Wednesday, October 23, 2002 5:00 PM > To: 'cygwin@cygwin.com' > Subject: cygwin 1.3.13, gcc 3.2 (no output) and gcc 2.95-3 (output but > no permission to execute) > > > Hi, > > I am having some difficulty with g++ after upgrading cygwin. > Here's a sample > > $ g++ -v foo.cpp > > [output snipped, in an attempt to get thru spam filter] > > Command returns error 1. It always returns error 1. > > A partial solution: > > I can just use gcc-2. However, the executables it generates > must be manually > adjusted to have correct permissions (i.e. using explorer). > > Sorry to be sparse on details. I can attach the cygcheck.out > file once I > figure out what the mailserver doesn't like. > > -- > 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/ > > -- 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/