octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54182] .o files created by mkoctfile should b


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #54182] .o files created by mkoctfile should be removed
Date: Tue, 26 Jun 2018 09:39:56 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0

Update of bug #54182 (project octave):

                  Status:                   Fixed => In Progress            
             Open/Closed:                  Closed => Open                   

    _______________________________________________________

Follow-up Comment #4:

After that change, cross-building for Windows with MXE Octave fails with the
following error:

src/x86_64-w64-mingw32-mkoctfile.cc: In function ‘int
octave_mkostemps_wrapper(char*, int)’:
src/x86_64-w64-mingw32-mkoctfile.cc:76:38: error: ‘O_BINARY’ was not
declared in this scope
   return mkostemps (tmpl, suffixlen, O_BINARY);
                                      ^~~~~~~~
src/x86_64-w64-mingw32-mkoctfile.cc:76:38: note: suggested alternative:
‘L_INCR’
   return mkostemps (tmpl, suffixlen, O_BINARY);
                                      ^~~~~~~~
                                      L_INCR
Makefile:27762: recipe for target 'src/x86_64-w64-mingw32-mkoctfile' failed


Gnulib's fcntl.h defines O_BINARY for that platform. [1]
Do we want to include gnulib headers when building mkoctfile?  I don't know
the background for not using our wrappers when cross-compiling.

[1]: https://www.gnu.org/software/gnulib/manual/html_node/fcntl_002eh.html

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54182>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]