From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: MSYS mode (continue)
Date: Mon, 29 Jul 2013 11:19:00 -0000 [thread overview]
Message-ID: <20130729111856.GD30069@calimero.vinschen.de> (raw)
In-Reply-To: <51F64B38.8000500@gmail.com>
On Jul 29 15:00, LRN wrote:
> On 29.07.2013 13:29, Corinna Vinschen wrote:
> > On Jul 27 20:17, NightStrike wrote:
> >> Perhaps it would be useful to actually identify which packages have
> >> extenuating needs. Maybe it's just one or two. Maybe it's all but
> >> one or two. I don't think that currently, the problem space is
> >> properly enumerated, but is instead living in the abstract.
> >
> > Very good point. This would perhaps show us much better where we're
> > heading here. From the current input I only see the following required
> > changes in relation to a stock Cygwin distro:
> >
> > - make w/ DOS path handling
> Yes. Note that the code DOES exist in make, but is disabled when make is
> built for Cygwin. One might question whether it was a good idea to
> disable support for W32 paths in make that runs on W32 (with a
> compatibility layer, but still...) in the first place.
Cygwin paths can contain "x:" as part of a normal filename.
> > - gcc targeting Mingw rather than Cygwin.
> You already have that, it's called "mingw cross-compiler for cygwin".
> And that is not what msys users use.
> I think you've meant something different here, i'm not sure what.
That's exactly what I meant. Of course we have a mingw cross compiler
in the Cygwin distro, but as far as the discussion on the mingw-w64 list
showed, MSYS users apparently prefer the "native" gcc compiler (the one
called "gcc") to produce mingw executables (aka "native Windows
exectables running without a compat layer") to avoid cross compiling
when creating native Windows executables. If the native gcc in an MSYS
install targets MSYS, and if you had to use a cross compiler to create
native Windows executables (as in Cygwin), there would ne no reason for
MSYS at all since it would be equivalent to Cygwin.
> > - Cygwin compiler provided as cross tool $arch-pc-cygwin-gcc, etc.(*)
> Yes. That includes binutils too (obviously)
>
>
> Also:
>
> base-files:
> add /mingw/bin to PATH when running in MINGW mode
> (adding /mingw/share/{man,info} to {MAN,INFO}PATH is also useful, but
> not really mandatory)
> (ok, these aren't binaries, so maybe they don't qualify)
>
> bash:
> Fix various instances of '\r' handling.
>
> coreutils:
> Bring back the '\r' support in md5sum. This is another change that might
> just go into Cygwin in general. I'm not sure whether '\r' is a valid
> character to use in filenames.
Yes.
> (optionally) embed install.exe.manifest into install.exe
>
> There are also patches to rebase that i find useful, but they are up to
> debate.
>
> Yeah, that list turned out to be really short. There may be other
> packages that need fixing ('\r' handling is the likely culprit), but i
> haven't bumped into them yet, so i wouldn't know.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2013-07-29 11:19 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABEPuQ+YxNF6LTAxRTVDQqQsKvGWGuaRxx1JAH62+wZZzgsC9w@mail.gmail.com>
[not found] ` <CABEPuQKRz2kamtrbBF5MjxPiSRMxwJ7NhG6wRrtRXMoBm+quNg@mail.gmail.com>
[not found] ` <20130704091632.GM5118@calimero.vinschen.de>
[not found] ` <CABEPuQKb8ZFvA=5947_JNQ3xZUNi98FTkV=9Q04f8vMY-4q1pg@mail.gmail.com>
[not found] ` <20130704101046.GN5118@calimero.vinschen.de>
[not found] ` <CABEPuQJ2S5jUbJDS+XUhrvdLtu6t53QAvsmQ_q5RbvELZxHJhw@mail.gmail.com>
[not found] ` <20130704103708.GA12995@calimero.vinschen.de>
[not found] ` <CABEPuQ+iF265-SQzfLTmsBegG+BVjpLPowxRAH8ioWv1Us_iYg@mail.gmail.com>
[not found] ` <20130704121617.GC12995@calimero.vinschen.de>
[not found] ` <20130704163612.GA4729@ednor.casa.cgf.cx>
2013-07-05 9:07 ` Corinna Vinschen
2013-07-05 16:42 ` Christopher Faylor
2013-07-11 11:17 ` Corinna Vinschen
2013-07-25 11:06 ` Alexey Pavlov
2013-07-25 11:11 ` Corinna Vinschen
2013-07-25 13:11 ` Charles Wilson
2013-07-25 15:02 ` Corinna Vinschen
2013-07-25 18:21 ` Charles Wilson
2013-07-25 18:33 ` Charles Wilson
2013-07-25 20:53 ` Christopher Faylor
2013-07-25 21:08 ` LRN
2013-07-25 21:31 ` Larry Hall (Cygwin Developers)
2013-07-26 1:55 ` Christopher Faylor
2013-07-26 4:03 ` LRN
2013-07-26 5:46 ` Christopher Faylor
2013-07-26 8:15 ` Corinna Vinschen
2013-07-26 15:14 ` Christopher Faylor
2013-07-26 15:48 ` LRN
2013-07-26 16:16 ` Corinna Vinschen
2013-07-26 16:12 ` Corinna Vinschen
2013-07-26 16:37 ` Christopher Faylor
2013-07-26 16:45 ` Daniel Colascione
2013-07-26 16:47 ` Corinna Vinschen
2013-07-26 17:01 ` Christopher Faylor
2013-07-26 17:03 ` Daniel Colascione
2013-07-26 17:36 ` Christopher Faylor
2013-07-26 23:12 ` Yaakov (Cygwin/X)
2013-07-27 3:07 ` Charles Wilson
2013-07-28 0:18 ` NightStrike
2013-07-29 9:30 ` Corinna Vinschen
2013-07-29 11:00 ` LRN
2013-07-29 11:19 ` Earnie Boyd
2013-07-29 12:20 ` Charles Wilson
2013-07-29 12:49 ` Corinna Vinschen
2013-07-29 14:22 ` Charles Wilson
2013-07-29 18:11 ` Larry Hall (Cygwin Developers)
2013-07-29 11:19 ` Corinna Vinschen [this message]
2013-07-29 15:36 ` LRN
2013-07-29 15:47 ` Corinna Vinschen
2013-07-29 16:37 ` Charles Wilson
2013-07-30 1:18 ` LRN
2013-07-30 0:45 ` LRN
2013-07-30 9:04 ` Corinna Vinschen
2013-07-30 9:32 ` Alexey Pavlov
2013-07-30 9:47 ` Corinna Vinschen
2013-07-30 10:27 ` Alexey Pavlov
2013-07-30 10:34 ` Corinna Vinschen
2013-07-30 10:59 ` Alexey Pavlov
2013-07-30 14:55 ` Christopher Faylor
2013-07-30 15:43 ` Christopher Faylor
2013-07-30 16:14 ` Christopher Faylor
2013-07-29 9:25 ` Corinna Vinschen
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=20130729111856.GD30069@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@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).