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=RkipIk
	PA/bFPtdYCIf4mpNS/YCDH4SsYQ2hcnaeWC7ok3GTcxf0efGyT3lU+Gf9rdmnEVc
	YTyearLFKYi6gbjehSRS6pItKOr88mYg8pToQJ/7tARoqYaZ84T3S0ivNL0OzPEs
	SGBqS6lbThVo3L+icbzdTOf7txVVwYTqI/6Ro=
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=lqnt26KP6lBH
	RyslPNhR7JYLfL4=; b=RKITP+KPwz711zZQfX8RNLVDX5r7Ck2gOrpjyo6Jp8K8
	B6BZ7cFkCVoh1suQHxl9Gyf59bXeFqE/AbsMbBzAwHkVh4iUfNvfnnw5U2KDjPvc
	K3pQsSbEj5WxfrLEgi6EWboPkZF8a/nqkDwz5qctuHP5C/a0uunpmcQuFNI6gJE=
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-pb0-f42.google.com
X-Received:	by 10.68.229.68 with SMTP id so4mr3085430pbc.110.1403257654919; Fri, 20 Jun 2014 02:47:34 -0700 (PDT)
Message-ID:	<53A40328.8010000@gmail.com>
Date:	Fri, 20 Jun 2014 17:47:20 +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:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: Question on gcc install
References:	<9D11C0FA97F94A69A68A45B7A449C70F AT HPDV7TNotebook>
In-Reply-To:	<9D11C0FA97F94A69A68A45B7A449C70F@HPDV7TNotebook>
X-IsSubscribed:	yes

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

On 6/20/2014 07:58, Arthur Schwarz wrote:
> Hi JonY;
>=20
> I hope that this clarifies some of the thing yous mentioned (as well as
> others unmentioned).
>=20
> None of the toolchains are multilib capable, so -m32/-m64 is not going
> to work. See also http://wiki.osdev.org/Target_Triplet
>    "> info gcc -> Option Index" shows -m32 and -m64 as valid=20
>    Options Are there plans to change the info files so that=20
>    they better represent the distributed versions of the=20
>    compiler?
>=20

Yes, they are valid options to gcc, but that does not mean gcc is able
to honor them. None of the builds are specifically set up for multilib.

> No, gdb happens to be invariant because you don't have cross gdb
> installed. You cannot debug 32bit code with 64bit gdb on Windows.
>    Would it be possible to clarify that 64-bit compiler target
>    Will only work on a compatible 64-bit gdb (same for 32-bit)
>    and that in order to get gcc to generate code for 32-bit
>    targets the setup-x86.exe must be used ant that in order to
>    get 64-bit target code setup-x86_64.exe must be used?
>=20
>=20

No, use the cross compilers, host and target triplets are not tied to
each other. You can easily run a 32bit compiler that targets 64bt etc,
eg x86_64-w64-mingw32-gcc on 32bit Cygwin.

>> If there is a resource document that I can look at to find the meaning of
>> life, could you tell me where to find it? I have downloaded the=20
>> gcc.gnu.org document set for vrs. 4.8.3, Is this sufficient?
>=20
> My advice is, stop jumping to conclusions,=20
>    Could you please clarify what in the above sentence draws a=20
>    conclusion? Are you saying that if I have concluded that
>    documentation exists that it does not?
>=20

You jump to conclusion about "version" strings and "triplets", assume
differences where there are none.

> and stop assuming facts about how things are related,=20
>    Could you please clarify what in the above sentence supports your=20
>    statement? Are you saying that the gcc documentation for vrs. 4.8.3
>    Is not related to the gcc port?
>=20

Just start using ${prefix}-gcc for cross compiles, and "gcc" for native
compiles, likewise for other frontend drivers.

>=20
>    What on Earth is the python script for?
>       It is for gdb pretty-printing. Your questions are more=20
>       appropriate on gcc-help.
>          Is there some reason a gdb script is located under
>          A gcc directory and not a gdb directory?
>=20

Because libstdc++ internal structures are tied to gcc, not gdb.

>=20
>    Supposing the following seems to have occurred with this release.
>       1: The use of appended version numbers in /bin has been=20
>          abandoned.

That is up to upstream gcc to decide, I don't control how the executable
end up as.

>       2: The latest distribution (16 Jun) has an error in that=20
>          x86_64-w64-mingw32 does not have an associated file=20
>          in /usr/. There is an associated file in /usr/lib/gcc=20
>          however.
>=20

It doesn't really matter where it goes, there is no meaning in it.

>       What?
>          In trying to understand your comment I assume that you
>          Are questioning items 1: and 2: above.=20
>          1: the latest download, unlike previous downloads, is
>              Missing compiler files such as=20
>              i686-pc-cygwin-gcc-4.8.2.exe.

Use "i686-pc-cygwin-gcc", so you don't have to mess around each and
every update.

>          2: In all cases except x86_64-w64-mingw32, there is
>             a directory in /usr and /usr/lib/gcc with the
>             same toolchain prefix as in /bin. Without being
>             tendentious I assume that you understand the
>             toolchain prefix as defined in=20
>             http://wiki.osdev.org/Target_Triplet. You have=20
>             requested that I make no assumptions, so I now
>             assume that the omission is deliberate and=20
>             need no further investigation or action.
>=20

That is right, because there is no hidden conspiracy theory behind it.

>    From http://wiki.osdev.org/Target_Triplet the compiler names
>    are:
>       machine-vendor-operatingsystem
>=20
>    For the cygwin distribution this translates to:
>         i686-pc-cygwin
>         |    |  o- operating system
>         |    o- vendor
>         o- target platform
>=20
>         x86_64-pc-cygwin
>         |      |  o- operating system
>         |      o- vendor
>         o- target platform
>=20
>         i686-pc-mingw32/
>         |    |  o- operating system
>         |    o- vendor
>         o- target platform
>=20
>         i686-w64-mingw32
>         |    |   o- operating system
>         |    o- vendor
>         o- target platform
>=20
>         x86_64-w64-mingw32
>         |      |   o- operating system
>         |      o- vendor
>         o- target platform
>=20
>        What is the w64 vendor and mingw32 operatingsystem?
>        I am relieved that the '32' in 'mingw32' has
>        no meaning.
>=20

mingw32 is a shorthand for "stuff that runs on Windows and uses msvcrt".
The "w64" signifies the "mingw32" implementation came from mingw-w64, as
opposed to the default "pc", where it came from mingw.org. Different
implementations of the same target.

>=20
>    /usr/share/doc/gcc/README and /usr/share/doc/gcc/INSTALL/README=20
>    Reference the directory gcc/doc. Would it be possible to show=20
>    the complete path to this directory?

It means <https://gcc.gnu.org/install/>.



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

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

iQIcBAEBAgAGBQJTpAMuAAoJEHE7X+KcFF1F90sP/0lUl5IFuLZYB4czCxrdtS94
PviqeYwDrnf6oCyXplPYxZf953Ha3LSRtHjtHWuJCNcB9G6LRZqrVtiE3WHKKUxf
xHu0xipwqUZyJa9HDTvfIGxSXvqCPbsBj8v0lxrDD7hf4FDtM3eYFJ6l7ESyKGgl
ph/4gXyTF3pSZWW2/OYof0fQH8FVOoV3K8K378Nc+Y+afl7eyoUvr9W5bAqVWRpt
G11jgrJcZhf+wfQJ+5FoVUnC67E4xNcLsOq5MbFsl5/14WZz8g8/xnyfQuPLVhOw
cOhj39p5KLkKYGSkfFf+zqTWxiM+EUvMFByyPpJUMLoFB9VShZpIbvGP2ov+6Ndd
RS598+XZZfiKfi7N1l+BZvK+RpALrwDnF2AFpfWPx3PqwKlvXEiauQVy7rEKNaVI
IO8nE1VqliEfstbFDQPU3YRGiCWQgvzybj85BqSxpVYIaJN/wRWaHrj2uUsg8ii8
zKYsJ2NkP1X+JGK8GR8FiQV7nwU7jloLlQg/ZvvBlqQ4j0tIgoRQ2M2YjmhrJkou
Z0FtpFOgZRbSFJ+zHi+oqd6czefJs/SY4sbNakyCfWARo8VsRq14L0FyWLtDaqJ+
fJtaawyBUwFmUbLIJvvBCvknX1AU55cHU2p6qO6qBM15wlc0tKzoVAgqAmRT+JSB
nOzLPrGdB5mh51rKyTYK
=EQpx
-----END PGP SIGNATURE-----

--TJfQF5tBhPSEV1gxgwihCCJLkB5lQgdgn--

- Raw text -