DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 32BFC3858D35
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Needing readline to build a local 64-bit exec
Thread-Topic: Needing readline to build a local 64-bit exec
Thread-Index: AdZj2Vp7OUz6X+FPTS23c2JOB830Ww==
Date: Mon, 27 Jul 2020 05:47:05 +0000
Message-ID: <AM6PR03MB3608D7496435C0738FFA91A3A4720@AM6PR03MB3608.eurprd03.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 545bac09-1618-4db0-063a-08d831f07e29
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Jul 2020 05:47:05.0485 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8EUR05HT242
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT,
 FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_PASS, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Fergus Daly via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Fergus Daly <fergusd84 AT outlook DOT com>
Cc: Fergus Daly <fergusd84 AT outlook DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

Of more than 640 *.c files incorporated into a locally-built executable, exactly one contains many references
to readline, such as "#include <readline/readline.h>". The 32-bit build proceeds impeccably to completion:
there is a subdirectory x86/release/readline in the Cygwin resource and a paragraph for @ readline in the file
x86/setup.ini, albeit with "obsolete" qualifiers.
However the 64-bit build fails at the compilation of the file containing the reference to readline: various *.h
not found. There is a subdirectory x86_64/release/readline in the resource but it contains only subdirectories, 
not the root readline-7.*.tar.xz files. The file x86_64/setup.ini contains no paragraph for @ readline.
I do not fully understand the interpretation or consequences of obsoletion, but this changed provision relating
to readline is the key difference between x86/ and x86_64/.
I tried supplementing the resource under x86_64/release/readline with the "missing" *.tar.xz files and editing x86_64/setup.ini to include the paragraph for @ readline, but this broke setup.ini.sig.
(I use a constantly updated mirror on a local drive. It takes 62G but it's worth it.)
It is clear (well, given my limited understanding of the handling of obsoleted files) that in some way the
provision under x86/release/readline and its referencing in x86/setup.ini remains critical to the successful build
of the 32-bit executable, and the lack of provision under x86_64/release/readline and omission from 
x86_64/setup.ini is critical to the failed build. It seems to be located, picked up and used, despite its obsolete
status?
Can it be recovered into the x86_64 provision?
Or can somebody who understands it better please explain the discrepancy in x86 and x86_64 provision
that triggers the contrasting success and failure for 32-bit and 64-bit version build attempts. And, even better,
how to achieve 64-bit success?
Thank you!    
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple