From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: headache on build repeatibility: octave vs BLODA ?
Date: Thu, 30 Jan 2020 21:34:00 -0000 [thread overview]
Message-ID: <3de58ab5-6779-9f59-6ee9-2fa4f4d0e36a@gmail.com> (raw)
In-Reply-To: <3ec4538b-3e45-43cc-b96e-a3b8be17bdb9@SystematicSw.ab.ca>
Am 30.01.2020 um 22:05 schrieb Brian Inglis:
> On 2020-01-29 06:46, Takashi Yano wrote:
>> Hi Marco,
>>
>> On Wed, 29 Jan 2020 13:19:11 +0100
>> Marco Atzeri wrote:
>>> As Octave uses gnulib, it is possible that the changes in MS are causing
>>> a different subset of gnulib to be used than before, may be exposing
>>> a latent bug or race.
>>>
>>> Unfortunately my old build tree was polluted by mistake, so I can
>>> not directly compare a good build tree versus a failing one.
>>
>> I found suspicious difference between the working build and the
>> not-working build.
>>
>> The not-working build has fflush.o, fseek.o and fseeko.o in
>> build/libgnu/.libs
>> directory, while the working build does not.
>>
>> Also, cygoctave-7.dll of not-working build exports rpl_fflush,
>> rpl_fseek and rpl_fseeko, while that of the working build does
>> not.
>>
>> As a test, I used following patch to forcibly remove the code
>> setting REPLACE_FSEEKO to 1 in configure script, and rebuilt
>> octave. This works without segmentation fault.
>
> For these to be considered missing or deficient such that they should be
> provided or replaced gnulib must consider Cygwin lacking support for ANSI C
> fflush https://www.gnu.org/software/gnulib/MODULES.html#ansic_enh_stdio
> and POSIX 2008 fseek and fseeko supporting pipes and 4GB in 32 bit mode
> https://www.gnu.org/software/gnulib/MODULES.html#posix_sup
> perhaps as a result of incorrect conclusions about Cygwin in autoreconf?
>
I was able to rebuild 5.1.0 successfully on a x86_64 cygwin1.dll
built from git source.
Nor flush or fseek gnulib modules were built.
During weekend I will replicate with i686.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-01-30 21:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 16:55 Marco Atzeri
2020-01-25 18:15 ` Brian Inglis
2020-01-27 6:54 ` Marco Atzeri
2020-01-25 20:36 ` Achim Gratz
2020-01-26 6:58 ` Marco Atzeri
2020-01-26 8:05 ` ASSI
2020-01-26 8:38 ` Marco Atzeri
2020-01-27 6:45 ` Marco Atzeri
2020-01-27 11:33 ` Takashi Yano
2020-01-28 6:41 ` Marco Atzeri
2020-01-28 14:55 ` Takashi Yano
2020-01-29 9:44 ` Corinna Vinschen
2020-01-29 12:19 ` Marco Atzeri
2020-01-29 13:46 ` Takashi Yano
2020-01-29 15:11 ` Takashi Yano
2020-01-29 15:32 ` Corinna Vinschen
2020-01-29 15:34 ` Corinna Vinschen
2020-01-29 16:08 ` Takashi Yano
2020-01-29 17:57 ` Corinna Vinschen
2020-01-30 21:05 ` Brian Inglis
2020-01-30 21:34 ` Marco Atzeri [this message]
2020-01-28 17:26 ` ASSI
2020-01-28 20:04 ` Marco Atzeri
2020-01-28 20:21 ` Achim Gratz
2020-01-26 2:42 ` Takashi Yano
2020-01-26 5:11 ` Takashi Yano
2020-01-26 10:24 ` Marco Atzeri
2020-01-26 10:31 ` Takashi Yano
2020-01-29 0:03 ` Hans-Bernhard Bröker
2020-01-29 0:39 ` Hans-Bernhard Bröker
2020-01-29 5:10 ` Marco Atzeri
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=3de58ab5-6779-9f59-6ee9-2fa4f4d0e36a@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).