X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=O+Xy2F
	4Nnn+OF9pUbuk8UZqPJKOv2g00oxNSuQbK2SL567F21YN6XDEkCniyVb57TlOt5q
	ghFpIUEFNVA2rj4X+SLBwYrNfxBH/6fAwqpTaoDp5jJLUBKhcFqMl41a/IL4bs26
	6CrrarB1xDaKGjiDXjj8+O4iCCJ3fXzcsXb98=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type; s=default; bh=kBezdIcSLOAF
	s90AhnrTWtgZ8ZI=; b=sDmGeDTZ0dakeQwhne7HMGE5UbNwtqVuKQtWWIh9nxtw
	mnpcPS0rYP4LRFDgNRME48M9elQcZFxvbvJRxin9DBehfRcUU2gyO6frTzbtD0wv
	wVC/kQ0f8snnm3/ScrfV7vvnxvJhEZtBcwr9rgfm07vgt70Rm0UKEfVYx340NE0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.1 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-pa0-f42.google.com
X-Received:	by 10.68.164.100 with SMTP id yp4mr914750pbb.136.1403129515236; Wed, 18 Jun 2014 15:11:55 -0700 (PDT)
Message-ID:	<53A20E9B.3040600@gmail.com>
Date:	Thu, 19 Jun 2014 06:11:39 +0800
From:	JonY <10walls AT gmail DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:24.0) Gecko/20140503 FossaMail/24.5.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Question on gcc install
References:	<124B6026BBED4E07BA053A1477FEC570 AT 2600kPC> <CAEhDDbCtjdCJpGLYzOV+-bXgaA=QHeHCcPGCi9m57Yc_5-DKEg AT mail DOT gmail DOT com> <F8570B1AB4F3448E953AB201979AAC39 AT 2600kPC>
In-Reply-To:	<F8570B1AB4F3448E953AB201979AAC39@2600kPC>
X-IsSubscribed:	yes

--6uo8Ns5BV4HfmEdHFWP1cP2J622vN6Qjr
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 6/18/2014 23:11, Arthur Schwarz wrote:
> I am including cygcheck.out as an attachment.=20
>=20
> Andrey Repin pointed out to me that my various e-mail responses are
> scattered all over the mailing list. I am very sorry for this and hope th=
at
> at least this e-mail is put in the appropriate place so that proper track=
ing
> can be done. If you have not seen my prior posts then some of the history
> and flavor of comments in this post may be lost.
>=20

Please don't add "--" to separate your text from others too, it is
treated as a signature in some clients.

> I don't think that there is an error in cygwin. I think that the number of
> executables, directories, etc. is by intent. What I am trying to do is to
> discover the intent and then, if necessary, report errors.
>=20
> Here are a list of guesses:
>    /bin
>       i686-pc-cygwin.*      Related toolchain for a compiler
>       i686-pc-mingw32.*     i686/x86 indicates the compiler instruction s=
et
>       i686-w64-mingw32.*    pc/w64 =3D 32/64-bits the input architecture =
(?)
>       x86_64-pc-cygwin.*    cygwin/mingw32 the compiler producer
>       x86_64-w64-mingw32.*
>=20
> It is also possible (again I'm guessing) the prefix represents the output
> architecture rather than the compiler architecture. This would (perhaps)
> explain why the gcc -m32 option has been disabled. If the -m32 option is =
not
> disabled by intent then there is a compiler bug, and if it is disabled by
> intent then this indicates a departure from behavior for a direct port.
>=20

None of the toolchains are multilib capable, so -m32/-m64 is not going
to work. See also http://wiki.osdev.org/Target_Triplet

> Each prefix has two related directories:
>    /usr   used by the compiler
>       i686-pc-cygwin/
>       i686-pc-mingw32/
>       i686-w64-mingw32
>       x86_64-pc-cygwin
>       x86_64-w64-mingw32
>=20
>    /usr/lib/gcc  contains version specific data for user (& compiler?)
>       i686-pc-cygwin/vrs/
>       i686-pc-mingw32/vrs/
>       i686-w64-mingw32/vrs/
>       x86_64-pc-cygwin/vrs/
>       x86_64-w64-mingw32/vrs/
>=20
> Prefixes with an appended version number in /bin are given as a visual
> indication of the version of the software associated with the prefix. For
> example, i686-pc-cygwin-gcc-4.8.2.exe indicates that the toolchain for
> i686-pc-cygwin is specific to gcc 4.8.2. I think that
> i686-pc-cygwin-gcc-4.8.2.exe is the same file as i686-pc-cygwin-gcc.exe.
>=20

Yes.

> Supposing the following seems to have occurred with this release.
> 1: The use of appended version numbers in /bin has been abandoned.
> 2: The latest distribution (16 Jun) has an error in that x86_64-w64-mingw=
32
> does not have an associated file in /usr/. There is an associated file in
> /usr/lib/gcc however.
>=20

What?

> What I would (ultimately) like to discover is resource material containing
> the exact expected configurations and the meanings for all the prefixes.

http://wiki.osdev.org/Target_Triplet

> What is what and what goes where. And I would like to have a resource rat=
her
> than wasting bandwidth on the mailing list. To this I would add that the
> information in /usr/share/doc/gcc is not specific to the installation on
> cygwin, and also that /usr/share/gcc-vrs/ has a nested python script. What
> on Earth is the python script for?
>=20

It is for gdb pretty-printing. Your questions are more appropriate on
gcc-help.



--6uo8Ns5BV4HfmEdHFWP1cP2J622vN6Qjr
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBAgAGBQJTog6iAAoJEHE7X+KcFF1FBrcP/0MnCTaxT80IZD13dOLqFXCL
gPCoU/9hv2okaINytD/ba6Av9y/d980o3bVTk2xkZyhDaCXS6Z/S9TsT9cMbUqaO
qPt71yqkxTDdnpTe7mg8UOUwwcLjq91YuFkv2fJDSjg1FPJ+aixFpcRZci+F0aOu
pwPxzadcjq4yNnioKLmZCGrMQJtmmC503fH5JNVpAkm/BwuJpVTxuk6fT9KF5lfQ
tD94hcs2v4hMOHk34ULQXBkibm+64rgtYGvUnPGAm53fPkCpE3vGgFUJYujXeswv
EH85F8nZglqvfWbwowgibSjzQQ5Cd28IyBN8EHWWqRBbe/IE1NxOoCA3105MzCe3
e3rDGFbxqgMNYBw0BVBomRgbQnnLWV9lzXQ7IesLDjJ9p/YVy/Pj0W6u49nIZ/90
XseVux+O3HdjKVeLkTBHJ8DAiKm41Nx/mjLsHYS/gny0NcdqhojiyTXb7e+BMFtI
CcRuCtcpKnBX0cLLL8eWar5NU/kUBGeW56+K8x7K281WQ9MndEtE6fHnSg+TF1mk
ekev17vegZwNDHzGHt6yxWNy4gcdHBQZQxhlOqvaRkT5QGwo6L5n7wSSpGkovtgH
jE1gFOCIUC5UIr5WFcyw8ap7Huo36vefr9nIAS0A1RVgH+0myUPBHYQuij5VJrxa
lxx0Z8od/yWKRZsGsapZ
=Cm7k
-----END PGP SIGNATURE-----

--6uo8Ns5BV4HfmEdHFWP1cP2J622vN6Qjr--

- Raw text -