From: Peter Rosin <peda@lysator.liu.se>
To: cygwin-apps@cygwin.com
Subject: Re: GCC dependencies (attn David Billinghurst)
Date: Sat, 13 Aug 2011 16:20:00 -0000 [thread overview]
Message-ID: <4E46A43B.5010905@lysator.liu.se> (raw)
In-Reply-To: <20110813112813.GD4098@calimero.vinschen.de>
Den 2011-08-13 13:28 skrev Corinna Vinschen:
> Hi Dave, Hi Yaakov,
>
> On Aug 12 11:21, Yaakov (Cygwin/X) wrote:
>> On Fri, 2011-08-12 at 16:48 +0100, Dave Korn wrote:
>>> Thanks. I'm not too sure about not installing the .la files; won't that
>>> potentially lead to problems for libtool-using projects at link time?
>>
>> No, but that reminded me, the libtool fixup script needs a small tweak
>> to adjust. I just pushed that to Ports git.
>>
>>> I just started a build and test cycle using your updated patches+cygport
>>> script; since you have about a million packages to maintain, I may as well
>>> take care of releasing this and free you up for other stuff.
>>
>> OK. FHI, last month, I tried sending the following patches upstream:
>>
>> top-level: fix config.rpath for cygwin/mingw
>> http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01578.html
>> http://sourceware.org/ml/binutils/2011-07/msg00181.html
>> http://sourceware.org/ml/gdb-patches/2011-07/msg00563.html
>>
>> cygwin/mingw: update LIBGCJ_SONAME
>> http://gcc.gnu.org/ml/gcc-patches/2011-07/msg01579.html
>>
>> libjava: add comment to libtool-version
>> http://gcc.gnu.org/ml/java-patches/2011-q3/msg00023.html
>>
>> AFAICS they've gone absolute nowhere. Maybe you'll have better luck.
>
> here's a minor nit, but that bugs me for a while now.
>
> $ cc hello.c
> $ ./a.out
> bash: ./a.out: No such file or directory
>
> I would like to see that GCC for Cygwin creates the output file
> "a.out.exe", so the result is the same on Unix/Linux and Cygwin:
It's "a.exe" for cygwin native.
> $ cc hello.c
> $ ./a.out
> hello, world
Cheers,
Peter
next prev parent reply other threads:[~2011-08-13 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 3:12 Yaakov (Cygwin/X)
2011-07-28 11:56 ` David Billinghurst
2011-07-29 23:37 ` Yaakov (Cygwin/X)
2011-07-30 0:26 ` Yaakov (Cygwin/X)
2011-08-09 18:45 ` Dave Korn
2011-08-09 21:46 ` David Billinghurst
2011-08-12 12:09 ` Yaakov (Cygwin/X)
2011-08-12 12:41 ` Yaakov (Cygwin/X)
2011-08-13 14:12 ` Corinna Vinschen
2011-08-14 19:30 ` Yaakov (Cygwin/X)
2011-08-15 4:03 ` Yaakov (Cygwin/X)
2011-08-15 7:42 ` Corinna Vinschen
2011-08-16 12:33 ` Dave Korn
2011-08-12 15:49 ` Dave Korn
2011-08-12 16:21 ` Yaakov (Cygwin/X)
2011-08-13 11:28 ` Corinna Vinschen
2011-08-13 16:20 ` Peter Rosin [this message]
2011-08-14 11:20 ` Corinna Vinschen
2011-08-14 23:01 ` Peter Rosin
2011-08-15 7:47 ` Corinna Vinschen
2011-10-16 21:19 ` Yaakov (Cygwin/X)
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=4E46A43B.5010905@lysator.liu.se \
--to=peda@lysator.liu.se \
--cc=cygwin-apps@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).