public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: headache on build repeatibility: octave vs BLODA ?
Date: Wed, 29 Jan 2020 13:46:00 -0000	[thread overview]
Message-ID: <20200129224653.b3238736661d3c95fc30ee5f@nifty.ne.jp> (raw)
In-Reply-To: <9e66f9f1-109f-7a3c-2c86-abd3ef7fc628@gmail.com>

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.

I do not look into the reason why this difference causes yet.

I would be happy if this could help.

--- m4/fseeko.m4.orig   2020-01-29 21:39:37.280507900 +0900
+++ m4/fseeko.m4        2020-01-29 21:36:29.263747100 +0900
@@ -30,16 +30,19 @@
     HAVE_FSEEKO=0
   else
     if test $WINDOWS_64_BIT_OFF_T = 1; then
-      REPLACE_FSEEKO=1
+      dnl REPLACE_FSEEKO=1
+      REPLACE_FSEEKO=0
     fi
     if test $gl_cv_var_stdin_large_offset = no; then
-      REPLACE_FSEEKO=1
+      dnl REPLACE_FSEEKO=1
+      REPLACE_FSEEKO=0
     fi
     m4_ifdef([gl_FUNC_FFLUSH_STDIN], [
       gl_FUNC_FFLUSH_STDIN
       case "$gl_cv_func_fflush_stdin" in
         *yes) ;;
-        *) REPLACE_FSEEKO=1 ;;
+        dnl *) REPLACE_FSEEKO=1 ;;
+        *) REPLACE_FSEEKO=0 ;;
       esac
     ])
   fi
--- m4/fflush.m4.orig   2020-01-29 21:40:07.546238000 +0900
+++ m4/fflush.m4        2020-01-29 21:38:02.079793700 +0900
@@ -16,7 +16,8 @@
   gl_FUNC_FFLUSH_STDIN
   case "$gl_cv_func_fflush_stdin" in
     *yes) ;;
-    *) REPLACE_FFLUSH=1 ;;
+    dnl *) REPLACE_FFLUSH=1 ;;
+    *) REPLACE_FFLUSH=0 ;;
   esac
 ])
 

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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

  reply	other threads:[~2020-01-29 13:46 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 [this message]
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
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=20200129224653.b3238736661d3c95fc30ee5f@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).