octave-3.3.50 built by mingw-gcc-4.4.0 cannot be executed.

[Tatsuro MATSUOKA-2]

Hello

I have built octave-3.3.50 mingw-gcc-4.4.0.

At the prompt I execute octave from the prompt

$ octave

$
 
Octave starts but finishes soon without any messages.
I have tried gdb traces.  Unfortunately liboctave.dll conflicts user.dll without striping debug
symbols.

However some information is obtained.

[New thread 3940.0x8c4]
warning: HEAP[octave.exe]:
warning: Invalid Address specified to RtlFreeHeap( 003F0000, 6FCB8FB8 )


set_liboctave_warning_with_id_handler (f=0x6e92ab78 <liboctinterp!_Z15warning_with_idPKcS0_z>)
    at ../../../../octave-3.3.50/libcruft/misc/lo-error.c:79

Benjamin have not been reported such errors so that the error intrinsic for my system.

Does anyone give me advises?

Regards

Tatsuro

Some of gdb traces.********************************************  
Breakpoint 1 at 0x4013b9: file ../../../octave-3.3.50/src/main.c, line 34.
(gdb) r
Starting program: c:\programs\octavebuild\bin/octave.exe
[New thread 3940.0x8c4]
warning: HEAP[octave.exe]:
warning: Invalid Address specified to RtlFreeHeap( 003F0000, 6FCB8FB8 )
  :
  :
Program received signal SIGTRAP, Trace/breakpoint trap.
0x7c94120f in ntdll!DbgUiConnectToDbg () from C:\WINDOWS\system32\ntdll.dll
  :
  :
61      {
(gdb) n
62        if (f)
(gdb) n
63          current_liboctave_error_handler = f;
(gdb) n
66      }
(gdb) n
0x6ea7b9eb in octave_main () from c:\programs\octavebuild\bin\liboctinterp.dll
(gdb) n
Single stepping until exit from function octave_main,
which has no line number information.
0x6ef4bbcc in xerbla_ () from c:\programs\octavebuild\bin\liboctinterp.dll
(gdb) n
Single stepping until exit from function xerbla_,
which has no line number information.
set_liboctave_warning_handler (f=0x6e92aba8 <liboctinterp!_Z7warningPKcz>)
    at ../../../../octave-3.3.50/libcruft/misc/lo-error.c:70
70      {
(gdb) n
71        if (f)
(gdb) n
72          current_liboctave_warning_handler = f;
(gdb) n
75      }
(gdb) n
0x6ea7b9f7 in octave_main () from c:\programs\octavebuild\bin\liboctinterp.dll
(gdb) n

0x6ea7b9f7 in octave_main () from c:\programs\octavebuild\bin\liboctinterp.dll
(gdb) n
Single stepping until exit from function octave_main,
which has no line number information.
0x6ef4bbd4 in xerbla_ () from c:\programs\octavebuild\bin\liboctinterp.dll
(gdb) n
Single stepping until exit from function xerbla_,
which has no line number information.
set_liboctave_warning_with_id_handler (f=0x6e92ab78 <liboctinterp!_Z15warning_with_idPKcS0_z>)
    at ../../../../octave-3.3.50/libcruft/misc/lo-error.c:79
79      {
(gdb) n
80        if (f)
(gdb) n
81          current_liboctave_warning_with_id_handler = f;
(gdb) n
84      }
(gdb) n
0x6ea7ba03 in octave_main () from c:\programs\octavebuild\bin\liboctinterp.dll
(gdb) n
Single stepping until exit from function octave_main,
which has no line number information.
warning: HEAP[octave.exe]:
warning: Invalid Address specified to RtlFreeHeap( 003F0000, 6FCB8FB8 )



--------------------------------------
Thanks 10 years!  Yahoo! Shopping and Yahoo! Auctions
http://pr.mail.yahoo.co.jp/ec10years/

[Tatsuro MATSUOKA-2]

Hello

--- Tatsuro MATSUOKA  wrote:
> I have built octave-3.3.50 mingw-gcc-4.4.0.
>
> At the prompt I execute octave from the prompt
>
> $ octave
>
> $
>  
> Octave starts but finishes soon without any messages.

This problem caused by the linker flags acquired from fltk-config.

  FLTK backend libs:    -L/c/Programs/OctaveBuild/lib -mwindows -Lc:/Programs/OctaveBuild/lib
-Lc:/Programs/WinDevTools/lib -Lc:/Programs/GnuWin32/lib -mno-cygwin -Wl,--enable-auto-import
-Wl,--enable-runtime-pseudo-reloc -lfltk_gl -lglu32-lopengl32 -lfltk -lpthread -lole32 -lcomctl32

The above incules -mwindows and this flag made it impossible to startup octave.

Similar problem occur console mode gnuplot 4.3 for windows with wxt terminal.
See

http://www.nabble.com/console-mode-gnuplot-for-windows-with-wxt-doen-not-work-(gnuplot-4.3---mingw)-td25536073.html

http://www.nabble.com/Patch-for-makefile.mgw-for-console-mode-of-gnuplot-4.3-for-windows-td25643747.html

First I have kick out this problem by tweaking wx-config, by which 'make' of gnuplot gets linker flag.
 However, this kind of tweaking is better to be avoided if possible.

I have discussed linker option problem with the developer of wxWidgets. He proposed to use
-Wl,--subsystem,console option to override of -mwindows.

In the gnuplot case, I now propose two patches
FIrst:
- WX_LIBS = $(shell wx-config --libs)
+ WX_LIBS = $(shell wx-config --libs | sed -e 's/ -Wl,--subsystem,windows -mwindows//')
Second:
  WX_LIBS = $(shell wx-config --libs)
+ ifdef PIPES
+ WX_LIBS += -Wl,--subsystem,console
+ endif

In case that I consider the patch for fltk-config for windows, is which way is better?

Regards

Tatsuro

--------------------------------------
Yahoo! JAPAN - Internet Security for teenagers and parents.
http://pr.mail.yahoo.co.jp/security/

[shaiay]

2009/9/29 Tatsuro MATSUOKA <tmacchant@...>:

> Hello
>
> --- Tatsuro MATSUOKA  wrote:
>> I have built octave-3.3.50 mingw-gcc-4.4.0.
>>
>> At the prompt I execute octave from the prompt
>>
>> $ octave
>>
>> $
>>
>> Octave starts but finishes soon without any messages.
>
> This problem caused by the linker flags acquired from fltk-config.
>
>  FLTK backend libs:    -L/c/Programs/OctaveBuild/lib -mwindows -Lc:/Programs/OctaveBuild/lib
> -Lc:/Programs/WinDevTools/lib -Lc:/Programs/GnuWin32/lib -mno-cygwin -Wl,--enable-auto-import
> -Wl,--enable-runtime-pseudo-reloc -lfltk_gl -lglu32-lopengl32 -lfltk -lpthread -lole32 -lcomctl32
>
> The above incules -mwindows and this flag made it impossible to startup octave.
>
> Similar problem occur console mode gnuplot 4.3 for windows with wxt terminal.
> See
>
> http://www.nabble.com/console-mode-gnuplot-for-windows-with-wxt-doen-not-work-(gnuplot-4.3---mingw)-td25536073.html
>
> http://www.nabble.com/Patch-for-makefile.mgw-for-console-mode-of-gnuplot-4.3-for-windows-td25643747.html
>
> First I have kick out this problem by tweaking wx-config, by which 'make' of gnuplot gets linker flag.
>  However, this kind of tweaking is better to be avoided if possible.
>
> I have discussed linker option problem with the developer of wxWidgets. He proposed to use
> -Wl,--subsystem,console option to override of -mwindows.
>
> In the gnuplot case, I now propose two patches
> FIrst:
> -       WX_LIBS = $(shell wx-config --libs)
> +       WX_LIBS = $(shell wx-config --libs | sed -e 's/ -Wl,--subsystem,windows -mwindows//')
> Second:
>        WX_LIBS = $(shell wx-config --libs)
> +       ifdef PIPES
> +               WX_LIBS += -Wl,--subsystem,console
> +       endif
>
> In case that I consider the patch for fltk-config for windows, is which way is better?
>

Hi

I have never used fltk with mingw, only cygwin, so I don't know :(
Did you try to compile with these flags? what were the results of
removing -mwindows -- did the fltk backend compile/run?

Shai

[Tatsuro MATSUOKA-2]

Hello

--- Shai Ayal  wrote:

> Hi
>
> I have never used fltk with mingw, only cygwin, so I don't know :(
> Did you try to compile with these flags? what were the results of
> removing -mwindows -- did the fltk backend compile/run?

Yes it work if I remove '-mwindows' flag from fltk-config. (Howeever, eigs.cc test causes segfault! in
the yesterday run).
 
It is also case for wxWidget case for gnuplot.  I discussed one of the wxWidget developer. I proposed
that -mwindows flag is to be removed from wx-config.  However, my proposal is rejected because most
users use native windows application.

Tweaking wx-config is easy but the tweaking without careful consideration is better to be avoided. I'm
afraid that it may cause unwanted results when I use wxWidget libraries for other applications.

In the case of fltk and octave, I think it would better to modify configure setting of octave than to
modify fltk-config.  That is because fltk is not only used for octave. So that change of default
setting should be avoided if possible.

How do other people think about this case ?

Regards

Tatsuro

--------------------------------------
Yahoo! JAPAN - Internet Security for teenagers and parents.
http://pr.mail.yahoo.co.jp/security/

[Tatsuro MATSUOKA-2]

Hello

--- Tatsuro MATSUOKA wrote:

> Yes it work if I remove '-mwindows' flag from fltk-config. (Howeever, eigs.cc test causes
> segfault! in
> the yesterday run).
>  
> It is also case for wxWidget case for gnuplot.  I discussed one of the wxWidget developer. I
> proposed
> that -mwindows flag is to be removed from wx-config.  However, my proposal is rejected because
> most
> users use native windows application.
>
> Tweaking wx-config is easy but the tweaking without careful consideration is better to be
> avoided. I'm
> afraid that it may cause unwanted results when I use wxWidget libraries for other applications.
>
> In the case of fltk and octave, I think it would better to modify configure setting of octave
> than to
> modify fltk-config.  That is because fltk is not only used for octave. So that change of default
> setting should be avoided if possible.
>
> How do other people think about this case ?

I have considered the patch

--- configure.in.orig 2009-09-12 19:52:06 +0900
+++ configure.in 2009-09-29 16:56:09 +0900
@@ -845,7 +845,7 @@
   warn_fltk_config="FLTK config script not found.  Native graphics will be disabled."
 else
   FLTK_CFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --cflags`"
-  FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags`"
+  FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags | sed -e 's/ -mwindows//'`"
   
   AC_MSG_CHECKING(for OpenGL support in FLTK)
   cat > conftest.cc <<EOF

******************************
By the patch

FLTK backend libs:    -L/c/Programs/OctaveBuild/lib -mwindows -Lc:/Programs/OctaveBuild/lib
-Lc:/Programs/WinDevTools/lib -Lc:/Programs/GnuWin32/lib -mno-cygwin -Wl,--enable-auto-import
-Wl,--enable-runtime-pseudo-reloc -lfltk_gl -lglu32-lopengl32 -lfltk -lpthread -lole32 -lcomctl32

  |
  |
  V

 FLTK backend libs:    -L/c/Programs/OctaveBuild/lib -Lc:/Programs/OctaveBuild/lib
-Lc:/Programs/WinDevTools/lib -Lc:/Programs/GnuWin32/lib -mno-cygwin -Wl,--enable-auto-import
-Wl,--enable-runtime-pseudo-reloc -lfltk_gl -lglu32 -lopengl32-lfltk -lpthread -lole32 -lcomctl32

Regards

Tatsuro

--------------------------------------
Yahoo! JAPAN - Internet Security for teenagers and parents.
http://pr.mail.yahoo.co.jp/security/

[Benjamin Lindner]

Tatsuro MATSUOKA wrote:

> Hello
>
> --- Tatsuro MATSUOKA  wrote:
>> I have built octave-3.3.50 mingw-gcc-4.4.0.
>>
>> At the prompt I execute octave from the prompt
>>
>> $ octave
>>
>> $
>>  
>> Octave starts but finishes soon without any messages.
>
> This problem caused by the linker flags acquired from fltk-config.
>
>   FLTK backend libs:    -L/c/Programs/OctaveBuild/lib -mwindows -Lc:/Programs/OctaveBuild/lib
> -Lc:/Programs/WinDevTools/lib -Lc:/Programs/GnuWin32/lib -mno-cygwin -Wl,--enable-auto-import
> -Wl,--enable-runtime-pseudo-reloc -lfltk_gl -lglu32-lopengl32 -lfltk -lpthread -lole32 -lcomctl32
>
> The above incules -mwindows and this flag made it impossible to startup octave.
>
> Similar problem occur console mode gnuplot 4.3 for windows with wxt terminal.
> See
>
> http://www.nabble.com/console-mode-gnuplot-for-windows-with-wxt-doen-not-work-(gnuplot-4.3---mingw)-td25536073.html
>
> http://www.nabble.com/Patch-for-makefile.mgw-for-console-mode-of-gnuplot-4.3-for-windows-td25643747.html
>
> First I have kick out this problem by tweaking wx-config, by which 'make' of gnuplot gets linker flag.
>  However, this kind of tweaking is better to be avoided if possible.
>
> I have discussed linker option problem with the developer of wxWidgets. He proposed to use
> -Wl,--subsystem,console option to override of -mwindows.

That's not the way to do it IMO.

> In the gnuplot case, I now propose two patches
> FIrst:
> - WX_LIBS = $(shell wx-config --libs)
> + WX_LIBS = $(shell wx-config --libs | sed -e 's/ -Wl,--subsystem,windows -mwindows//')
> Second:
>   WX_LIBS = $(shell wx-config --libs)
> + ifdef PIPES
> + WX_LIBS += -Wl,--subsystem,console
> + endif
>
> In case that I consider the patch for fltk-config for windows, is which way is better?

As in the gnuplot issue, the former.

benjamin

[Benjamin Lindner]

Tatsuro MATSUOKA wrote:

> Hello
>
> --- Tatsuro MATSUOKA wrote:
>
>> Yes it work if I remove '-mwindows' flag from fltk-config. (Howeever, eigs.cc test causes
>> segfault! in
>> the yesterday run).
>>  
>> It is also case for wxWidget case for gnuplot.  I discussed one of the wxWidget developer. I
>> proposed
>> that -mwindows flag is to be removed from wx-config.  However, my proposal is rejected because
>> most
>> users use native windows application.
>>
>> Tweaking wx-config is easy but the tweaking without careful consideration is better to be
>> avoided. I'm
>> afraid that it may cause unwanted results when I use wxWidget libraries for other applications.
>>
>> In the case of fltk and octave, I think it would better to modify configure setting of octave
>> than to
>> modify fltk-config.  That is because fltk is not only used for octave. So that change of default
>> setting should be avoided if possible.
>>
>> How do other people think about this case ?
>

For the mingw binaries, since I need to build fltk from source, I can
remove the -mwindows flag there from fltk-config, so I would't need to
have it dealt with in octave's configure script.

Does this problem also occur on cygwin?

If we deal with this in octave's configure script, then I'd suggest it
be done only for mingw (and cygwn?) platform.

>
> I have considered the patch
>
> --- configure.in.orig 2009-09-12 19:52:06 +0900
> +++ configure.in 2009-09-29 16:56:09 +0900
> @@ -845,7 +845,7 @@
>    warn_fltk_config="FLTK config script not found.  Native graphics will be disabled."
>  else
>    FLTK_CFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --cflags`"
> -  FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags`"
> +  FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags | sed -e 's/ -mwindows//'`"

I'd suggest

sed -e "+s-mwindows++g"

to be more robust.

[Tatsuro MATSUOKA-2]

Hello

--- Shai Ayal wrote:
>
> I have never used fltk with mingw, only cygwin, so I don't know :(
> Did you try to compile with these flags? what were the results of
> removing -mwindows -- did the fltk backend compile/run?
>
>From the cygwin-1.7 prompt

$ $ fltk-config --use-gl --ldflags
-L/usr/local/lib -mwindows -Wl,--enable-auto-import -Wl,--enable-runtime-pseudo-reloc -lfltk_gl
-lglu32 -lopengl32 -lfltk -lpthread -lole32 -luuid -lcomctl32

This fltk is installed by setup-1.7.exe.

The '-mwindows' option is not deleted.

Hi Marco.
In the cygwin case, is not the -mwindow option harmful for building octave in the development branch ?

You can follow the context the below
http://www.nabble.com/octave-3.3.50-built-by-mingw-gcc-4.4.0-cannot-be-executed.-td25569527.html

Regards

Tatsuro  


--------------------------------------
Yahoo! JAPAN - Internet Security for teenagers and parents.
http://pr.mail.yahoo.co.jp/security/

[Marco atzeri-3]

> Da: Tatsuro MATSUOKA <tmacchant@...>
> Oggetto: Re: fltk-config for windows gives -mwindows flag (was octave-3.3.50  built by mingw-gcc-4.4.0 cannot be executed.)
> A: "Marco Atzeri" <marco_atzeri@...>
> Cc: maintainers@..., "Shai Ayal" <shaiay@...>
> Data: Mercoledì 30 settembre 2009, 09:18
> Hello
>
> --- Shai Ayal wrote:
> >
> > I have never used fltk with mingw, only cygwin, so I
> don't know :(
> > Did you try to compile with these flags? what were the
> results of
> > removing -mwindows -- did the fltk backend
> compile/run?
> >
> From the cygwin-1.7 prompt
>
> $ $ fltk-config --use-gl --ldflags
> -L/usr/local/lib -mwindows -Wl,--enable-auto-import
> -Wl,--enable-runtime-pseudo-reloc -lfltk_gl
> -lglu32 -lopengl32 -lfltk -lpthread -lole32 -luuid
> -lcomctl32
>
> This fltk is installed by setup-1.7.exe.
>
> The '-mwindows' option is not deleted.
>
> Hi Marco.
> In the cygwin case, is not the -mwindow option harmful for
> building octave in the development branch ?
>
> You can follow the context the below
> http://www.nabble.com/octave-3.3.50-built-by-mingw-gcc-4.4.0-cannot-be-executed.-td25569527.html

Hi Tatsuro,
currently fltk don't work on cygwin; at least for me.
The windows is created but only garbage is plotted.

I presume it is due to the available fltk
that is the not X11 version while the other GL
graphics library are X11.

So for the time being all my test are built with

../octave/configure --enable-float-truncate --libexecdir=/usr/lib --enable-shared --without-fltk --without-framework-opengl CFLAGS=-Dtimezone=_timezone CC="gcc-4 -shared-libgcc" F77=gfortran-4 CXX=g++-4 CPP=cpp-4

>
> Regards
>
> Tatsuro   

Marco



     

[Tatsuro MATSUOKA-2]

Hello

--- Marco Atzeri  wrote:

> Hi Tatsuro,
> currently fltk don't work on cygwin; at least for me.
> The windows is created but only garbage is plotted.
>
> I presume it is due to the available fltk
> that is the not X11 version while the other GL
> graphics library are X11.
>
> So for the time being all my test are built with
>
> ../octave/configure --enable-float-truncate --libexecdir=/usr/lib --enable-shared --without-fltk
> --without-framework-opengl CFLAGS=-Dtimezone=_timezone CC="gcc-4 -shared-libgcc" F77=gfortran-4
> CXX=g++-4 CPP=cpp-4
>

 Thank you for your reply.
I will propose the patch for mingw only.

Regards

Tatsuro


--------------------------------------
Yahoo! JAPAN - Internet Security for teenagers and parents.
http://pr.mail.yahoo.co.jp/security/

[Tatsuro MATSUOKA-2]

Hello


--- Benjamin Lindner  wrote:

> For the mingw binaries, since I need to build fltk from source, I can
> remove the -mwindows flag there from fltk-config, so I would't need to
> have it dealt with in octave's configure script.
>
> Does this problem also occur on cygwin?
>
> If we deal with this in octave's configure script, then I'd suggest it
> be done only for mingw (and cygwn?) platform.
>
> sed -e "+s-mwindows++g"

The above is typo. sed -e "s+-mwindows++g" is correct.

--- Marco Atzeri  wrote:

> Hi Tatsuro,
> currently fltk don't work on cygwin; at least for me.
> The windows is created but only garbage is plotted.

Although Benjamin said "so I would't need to have it dealt with in octave's configure script", I
propose here the patch for FLTK_LDFLAGS.

Regards

Tatsuro

--------------------------------------
Yahoo! JAPAN - Internet Security for teenagers and parents.
http://pr.mail.yahoo.co.jp/security/

[Tatsuro MATSUOKA-2]

Hello John

--- Tatsuro MATSUOKA wrote:
>
> Although Benjamin said "so I would't need to have it dealt with in octave's configure script", I
> propose here the patch for FLTK_LDFLAGS.
>
> Regards
>
> Tatsuro

http://www.nabble.com/Re%3A-fltk-config-for-windows-gives--mwindows-flag-(was-octave-3.3.50-built-by-mingw-gcc-4.4.0-cannot-be-executed.)-p25679117.html

Could you please reply me whether my proposal is accepted or not ?

My building script of octave for development branch depends on the patch being accepted or not.

In case of rejection, I should add a few context of hacking  of fltk-config in my build script.

Regards

Tatsuro

--------------------------------------
Yahoo! JAPAN - Internet Security for teenagers and parents.
http://pr.mail.yahoo.co.jp/security/

[Benjamin Lindner]

>> For the mingw binaries, since I need to build fltk from source, I can
>> remove the -mwindows flag there from fltk-config, so I would't need to
>> have it dealt with in octave's configure script.
>>
>> Does this problem also occur on cygwin?
>>
>> If we deal with this in octave's configure script, then I'd suggest it
>> be done only for mingw (and cygwn?) platform.
>>
>> sed -e "+s-mwindows++g"
> The above is typo. sed -e "s+-mwindows++g" is correct.

You are right, sorry.

>
>> Hi Tatsuro,
>> currently fltk don't work on cygwin; at least for me.
>> The windows is created but only garbage is plotted.
>
> Although Benjamin said "so I would't need to have it dealt with in octave's configure script", I
> propose here the patch for FLTK_LDFLAGS.

You can avoid the code duplication in the call to fltk-config by doing

diff -r a65c135a1deb configure.in
--- a/configure.in      Mon Oct 05 19:22:13 2009 +0200
+++ b/configure.in      Mon Oct 05 20:30:33 2009 +0200
@@ -847,6 +847,11 @@
    FLTK_CFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --cflags`"
    FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags`"

+  case "$canonical_host_type" in
+  *-*-mingw*)
+    FLTK_LDFLAGS="`echo $FLTK_LDFLAGS | sed -e 's+-mwindows++g'`"
+  esac
+
    AC_MSG_CHECKING(for OpenGL support in FLTK)
    cat > conftest.cc <<EOF
    #include <FL/gl.h>


benjamin

[Tatsuro MATSUOKA-2]

Hello

--- Benjamin Lindner  wrote:

> You can avoid the code duplication in the call to fltk-config by doing
>
> diff -r a65c135a1deb configure.in
> --- a/configure.in      Mon Oct 05 19:22:13 2009 +0200
> +++ b/configure.in      Mon Oct 05 20:30:33 2009 +0200
> @@ -847,6 +847,11 @@
>     FLTK_CFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --cflags`"
>     FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags`"
>
> +  case "$canonical_host_type" in
> +  *-*-mingw*)
> +    FLTK_LDFLAGS="`echo $FLTK_LDFLAGS | sed -e 's+-mwindows++g'`"
> +  esac
> +
>     AC_MSG_CHECKING(for OpenGL support in FLTK)
>     cat > conftest.cc <<EOF
>     #include <FL/gl.h>

Thanks!!

Regards

Tatsuro

--------------------------------------
GyaO! - Anime, Dramas, Movies, and Music videos [FREE]
http://pr.mail.yahoo.co.jp/gyao/

[John W. Eaton-3]

On 29-Sep-2009, Benjamin Lindner wrote:

| I'd suggest
|
| sed -e "+s-mwindows++g"
|
| to be more robust.

Why do you say that is more robust?  If the pattern is a literal
string, then I think the only requirement is that the delimiters for
the sed command don't appaer in the pattern string.

jwe

[John W. Eaton-3]

On  5-Oct-2009, Benjamin Lindner wrote:

| >> For the mingw binaries, since I need to build fltk from source, I can
| >> remove the -mwindows flag there from fltk-config, so I would't need to
| >> have it dealt with in octave's configure script.
| >>
| >> Does this problem also occur on cygwin?
| >>
| >> If we deal with this in octave's configure script, then I'd suggest it
| >> be done only for mingw (and cygwn?) platform.
| >>
| >> sed -e "+s-mwindows++g"
| > The above is typo. sed -e "s+-mwindows++g" is correct.
|
| You are right, sorry.
|
| >
| >> Hi Tatsuro,
| >> currently fltk don't work on cygwin; at least for me.
| >> The windows is created but only garbage is plotted.
| >
| > Although Benjamin said "so I would't need to have it dealt with in octave's configure script", I
| > propose here the patch for FLTK_LDFLAGS.
|
| You can avoid the code duplication in the call to fltk-config by doing
|
| diff -r a65c135a1deb configure.in
| --- a/configure.in      Mon Oct 05 19:22:13 2009 +0200
| +++ b/configure.in      Mon Oct 05 20:30:33 2009 +0200
| @@ -847,6 +847,11 @@
|     FLTK_CFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --cflags`"
|     FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags`"
|
| +  case "$canonical_host_type" in
| +  *-*-mingw*)
| +    FLTK_LDFLAGS="`echo $FLTK_LDFLAGS | sed -e 's+-mwindows++g'`"
| +  esac
| +
|     AC_MSG_CHECKING(for OpenGL support in FLTK)
|     cat > conftest.cc <<EOF
|     #include <FL/gl.h>

Only *-*-mingw*?  Would this also be a problem for *-*-msdosmsvc?

jwe

[Benjamin Lindner]

John W. Eaton wrote:

> On 29-Sep-2009, Benjamin Lindner wrote:
>
> | I'd suggest
> |
> | sed -e "+s-mwindows++g"
> |
> | to be more robust.
>
> Why do you say that is more robust?  If the pattern is a literal
> string, then I think the only requirement is that the delimiters for
> the sed command don't appaer in the pattern string.

It's not about the delimiters, it's about the removed space character.

Tatsuro originally suggested
    sed -e 's/ -mwindows//'
which sould only match if there is at least one space character
preceeding the token "-mwindows", correct?

IMO the replacement rule should remove "-mwindows" regardless if it is
preceeded by a space or not (e.g. even if it is the first token in a string)

benjamin

[Tatsuro MATSUOKA-2]

Hello

--- "John W. Eaton" wrote:

> Only *-*-mingw*?  Would this also be a problem for *-*-msdosmsvc?
>
> jwe
>

Similar problem may occur on msvc. However, the linker options of msvc have different style from those
of mingw.  I do not know how fltk-config for msvc pull the output of the msvc linker options.
Therefore I limit my patch to the mingw case.


Regards

Tatsuro      

--------------------------------------
GyaO! - Anime, Dramas, Movies, and Music videos [FREE]
http://pr.mail.yahoo.co.jp/gyao/

[Michael Goffioul-2]

On Sun, Oct 11, 2009 at 4:12 PM, John W. Eaton <jwe@...> wrote:

> | diff -r a65c135a1deb configure.in
> | --- a/configure.in      Mon Oct 05 19:22:13 2009 +0200
> | +++ b/configure.in      Mon Oct 05 20:30:33 2009 +0200
> | @@ -847,6 +847,11 @@
> |     FLTK_CFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --cflags`"
> |     FLTK_LDFLAGS="`$FLTK_CONFIG $fltkconf_args --use-gl --ldflags`"
> |
> | +  case "$canonical_host_type" in
> | +  *-*-mingw*)
> | +    FLTK_LDFLAGS="`echo $FLTK_LDFLAGS | sed -e 's+-mwindows++g'`"
> | +  esac
> | +
> |     AC_MSG_CHECKING(for OpenGL support in FLTK)
> |     cat > conftest.cc <<EOF
> |     #include <FL/gl.h>
>
> Only *-*-mingw*?  Would this also be a problem for *-*-msdosmsvc?

No. The -mwindows flag is only GCC specific.

Michael.

[Michael Goffioul-2]

2009/10/11 Tatsuro MATSUOKA <tmacchant@...>:

> Hello
>
> --- "John W. Eaton" wrote:
>
>> Only *-*-mingw*?  Would this also be a problem for *-*-msdosmsvc?
>>
>> jwe
>>
>
> Similar problem may occur on msvc. However, the linker options of msvc have different style from those
> of mingw.  I do not know how fltk-config for msvc pull the output of the msvc linker options.

There's no fltk-config for MSVC. I have one, because I compile FLTK
with my own toolchain that makes MSVC looks like GCC. But the
official FLTK build system for MSVC simply uses VS solution files.
No shell, no configure script, no fltk-config...

So in practice, my fltk-config script is simply as I want it to be.

Michael.