MXE: qt error with native build

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|

MXE: qt error with native build

PhilipNienhuis
Philip@DeskPRN ~/mxe-octave
$ hg summary
parent: 3066:23e3e2955cf5 tip
 Change Qt CONFIGURE_INCLUDE/LIBPATH_OPTION variable to be native only
branch: default
commit: 1 modified, 4 unknown
update: (current)

Win XP SP3.
I did:

hg clone .......
cd mxe-octave
autoconf
configure --enable-native-gcc --enable-native-build
mk-dist --jobs 1

Build runs fine until it gets at qt; last part of log:

:
# need to 'install' mkspecs for the native mingw to build during its build
if [ "yes" = yes ]; then cp -r '/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/mkspecs' '/home/Philip/mxe-octave/usr/i686-pc-mingw32/'; fi
make -C '/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3' -j '1'
make[2]: Entering directory `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/bin/qmake X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3//projects.pro  -o Makefile -spec win32-g++
"make" -w -- JOBS=1 -f Makefile
make[3]: Entering directory `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[3]: *** No rule to make target `-f'.  Stop.
make[3]: Leaving directory `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[1]: *** [build-only-qt] Error 2
make[1]: Leaving directory `/home/Philip/mxe-octave'

Apparently there's a hickup in the macro creating the "make" command? (the space between "--" and "JOBS=1"

Philip
Reply | Threaded
Open this post in threaded view
|

RE: MXE: qt error with native build

John Donoghue-3

Message: 5
Date: Thu, 20 Jun 2013 09:45:54 -0700 (PDT)
From: PhilipNienhuis <[hidden email]>
To: [hidden email]
Subject: MXE: qt error with native build
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Philip@DeskPRN ~/mxe-octave
$ hg summary
parent: 3066:23e3e2955cf5 tip
 Change Qt CONFIGURE_INCLUDE/LIBPATH_OPTION variable to be native only
branch: default
commit: 1 modified, 4 unknown
update: (current)

Win XP SP3.
I did:

hg clone .......
cd mxe-octave
autoconf
configure --enable-native-gcc --enable-native-build mk-dist --jobs 1

Build runs fine until it gets at qt; last part of log:

:
# need to 'install' mkspecs for the native mingw to build during its build
if [ "yes" = yes ]; then cp -r
'/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/mkspecs'
'/home/Philip/mxe-octave/usr/i686-pc-mingw32/'; fi make -C
'/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
-j '1'
make[2]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3//projects.pro
-o Makefile -spec win32-g++
"make" -w -- JOBS=1 -f Makefile
make[3]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[3]: *** No rule to make target `-f'.  Stop.
make[3]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[1]: *** [build-only-qt] Error 2
make[1]: Leaving directory `/home/Philip/mxe-octave'

Apparently there's a hickup in the macro creating the "make" command? (the
space between "--" and "JOBS=1"

Philip


------------------------------

It does the same on mine
Running just normal 'make' to create octave works fine though

Reply | Threaded
Open this post in threaded view
|

Re: MXE: qt error with native build

John W. Eaton
Administrator
On 06/20/2013 02:03 PM, John D wrote:

> Build runs fine until it gets at qt; last part of log:
>
> :
> # need to 'install' mkspecs for the native mingw to build during its build
> if [ "yes" = yes ]; then cp -r
> '/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/mkspecs'
> '/home/Philip/mxe-octave/usr/i686-pc-mingw32/'; fi make -C
> '/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
> -j '1'
> make[2]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
> -4.8.3/bin/qmake
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
> -4.8.3//projects.pro
> -o Makefile -spec win32-g++
> "make" -w -- JOBS=1 -f Makefile

What is in the generated specs file?  Where does the "-w -- JOBS=1" come
from?

jwe

Reply | Threaded
Open this post in threaded view
|

RE: MXE: qt error with native build

John Donoghue-3
In reply to this post by John Donoghue-3


-----Original Message-----
From: John D [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 2:03 PM
To: [hidden email]
Cc: 'PhilipNienhuis'
Subject: RE: MXE: qt error with native build


Message: 5
Date: Thu, 20 Jun 2013 09:45:54 -0700 (PDT)
From: PhilipNienhuis <[hidden email]>
To: [hidden email]
Subject: MXE: qt error with native build
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Philip@DeskPRN ~/mxe-octave
$ hg summary
parent: 3066:23e3e2955cf5 tip
 Change Qt CONFIGURE_INCLUDE/LIBPATH_OPTION variable to be native only
branch: default
commit: 1 modified, 4 unknown
update: (current)

Win XP SP3.
I did:

hg clone .......
cd mxe-octave
autoconf
configure --enable-native-gcc --enable-native-build mk-dist --jobs 1

Build runs fine until it gets at qt; last part of log:

:
# need to 'install' mkspecs for the native mingw to build during its build
if [ "yes" = yes ]; then cp -r
'/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/mkspecs'
'/home/Philip/mxe-octave/usr/i686-pc-mingw32/'; fi make -C
'/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
-j '1'
make[2]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3//projects.pro
-o Makefile -spec win32-g++
"make" -w -- JOBS=1 -f Makefile
make[3]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[3]: *** No rule to make target `-f'.  Stop.
make[3]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
make[1]: *** [build-only-qt] Error 2
make[1]: Leaving directory `/home/Philip/mxe-octave'

Apparently there's a hickup in the macro creating the "make" command? (the
space between "--" and "JOBS=1"

Philip


------------------------------

It does the same on mine
Running just normal 'make' to create octave works fine though


--------------------------------------

We could unexport MAKEFLAGS in the mxe-octave  Makefile.in, however are
there other options we will want to pass in via make that will need be
passed down recursively elsewhere?

Reply | Threaded
Open this post in threaded view
|

RE: MXE: qt error with native build

John Donoghue-3
In reply to this post by John W. Eaton


-----Original Message-----
From: John W. Eaton [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 2:19 PM
To: John D
Cc: [hidden email]; 'PhilipNienhuis'; [hidden email]
Subject: Re: MXE: qt error with native build

On 06/20/2013 02:03 PM, John D wrote:

> Build runs fine until it gets at qt; last part of log:
>
> :
> # need to 'install' mkspecs for the native mingw to build during its
> build if [ "yes" = yes ]; then cp -r
>
'/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/mkspecs'

> '/home/Philip/mxe-octave/usr/i686-pc-mingw32/'; fi make -C
> '/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
> -j '1'
> make[2]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src
> -4.8.3/bin/qmake
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src
> -4.8.3//projects.pro
> -o Makefile -spec win32-g++
> "make" -w -- JOBS=1 -f Makefile

What is in the generated specs file?  Where does the "-w -- JOBS=1" come
from?

jwe


-------------

JOBS=1 comes from ./mk-spec

According to gnu make manual, -w is automatically added when -C is used.

Running a normal make , rather than ./mk-dist also adds the -w option but it
doesn't seem to cause issues with qt and cause it to add  the '--'.



Reply | Threaded
Open this post in threaded view
|

Re: MXE: qt error with native build

PhilipNienhuis
In reply to this post by John Donoghue-3
John D wrote:
<snip>

> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
> -4.8.3//projects.pro
> -o Makefile -spec win32-g++
> "make" -w -- JOBS=1 -f Makefile
> make[3]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
> make[3]: *** No rule to make target `-f'.  Stop.
> ------------------------------
>
> It does the same on mine
> Running just normal 'make' to create octave works fine though

Not here:

:
make[8]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugins/imageformats/mng'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugins/imageformats/mng/mng.pro
  -o Makefile -spec win32-g++
Project ERROR: Package libmng not found
make[8]: *** [all] Error 2

Philip
Reply | Threaded
Open this post in threaded view
|

RE: MXE: qt error with native build

John Donoghue-3


-----Original Message-----
From: Philip Nienhuis [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 4:11 PM
To: John D
Cc: [hidden email]
Subject: Re: MXE: qt error with native build

John D wrote:
<snip>

> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src
> -4.8.3//projects.pro
> -o Makefile -spec win32-g++
> "make" -w -- JOBS=1 -f Makefile
> make[3]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
> make[3]: *** No rule to make target `-f'.  Stop.
> ------------------------------
>
> It does the same on mine
> Running just normal 'make' to create octave works fine though

Not here:

:
make[8]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/src/plugins/imageformats/mng/mng.pro
  -o Makefile -spec win32-g++
Project ERROR: Package libmng not found
make[8]: *** [all] Error 2

Philip

-----


That's from running make from the mxe-octave root directory?


Reply | Threaded
Open this post in threaded view
|

RE: MXE: qt error with native build

John Donoghue-3
In reply to this post by PhilipNienhuis


-----Original Message-----
From: Philip Nienhuis [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 4:11 PM
To: John D
Cc: [hidden email]
Subject: Re: MXE: qt error with native build

John D wrote:
<snip>

> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src
> -4.8.3//projects.pro
> -o Makefile -spec win32-g++
> "make" -w -- JOBS=1 -f Makefile
> make[3]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
> make[3]: *** No rule to make target `-f'.  Stop.
> ------------------------------
>
> It does the same on mine
> Running just normal 'make' to create octave works fine though

Not here:

:
make[8]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/src/plugins/imageformats/mng/mng.pro
  -o Makefile -spec win32-g++
Project ERROR: Package libmng not found
make[8]: *** [all] Error 2

Philip

-----

Have you set PKG_CONFIG_PATH to
`/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig  ?



Reply | Threaded
Open this post in threaded view
|

Re: MXE: qt error with native build

PhilipNienhuis
In reply to this post by John Donoghue-3
John D wrote:

>
>
> -----Original Message-----
> From: Philip Nienhuis [mailto:[hidden email]]
> Sent: Thursday, June 20, 2013 4:11 PM
> To: John D
> Cc: [hidden email]
> Subject: Re: MXE: qt error with native build
>
> John D wrote:
> <snip>
>> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
>> ce-src
>> -4.8.3//projects.pro
>> -o Makefile -spec win32-g++
>> "make" -w -- JOBS=1 -f Makefile
>> make[3]: Entering directory
>> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
>> make[3]: *** No rule to make target `-f'.  Stop.
>> ------------------------------
>>
>> It does the same on mine
>> Running just normal 'make' to create octave works fine though
>
> Not here:
>
> :
> make[8]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
> ns/imageformats/mng'
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
> -4.8.3/bin/qmake
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
> -4.8.3/src/plugins/imageformats/mng/mng.pro
>    -o Makefile -spec win32-g++
> Project ERROR: Package libmng not found
> make[8]: *** [all] Error 2
>
> Philip
>
> -----
>
>
> That's from running make from the mxe-octave root directory?

Of course.
It wasn't obvious to me from what other subdir I should run make.

I suppose ~/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3 ?
(just tried - see below)

<from your other email:>
 >
 > Have you set PKG_CONFIG_PATH to
 > `/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig  ?

No, but after checking I'll rather set it to:
/home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig


(Hmmmm just tried the above - I still get:

:
cd mng/ && make -f Makefile
make[3]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugins/imageformats/mng'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugins/imageformats/mng/mng.pro
  -o Makefile -spec win32-g++
'pkg-config' is not recognized as an internal or external command,
operable program or batch file.
Project ERROR: Package libmng not found
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugins/imageformats/mng'
make[2]: *** [sub-mng-make_default] Error 2
make[2]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugins/imageformats'
make[1]: *** [sub-imageformats-make_default] Error 2
make[1]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugins'
make: *** [sub-plugins-make_default-ordered] Error 2

 From where should I start over?

Thanks,

P.
Reply | Threaded
Open this post in threaded view
|

RE: MXE: qt error with native build

John Donoghue-3


-----Original Message-----
From: Philip Nienhuis [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 4:56 PM
To: John D
Cc: [hidden email]
Subject: Re: MXE: qt error with native build

John D wrote:

>
>
> -----Original Message-----
> From: Philip Nienhuis [mailto:[hidden email]]
> Sent: Thursday, June 20, 2013 4:11 PM
> To: John D
> Cc: [hidden email]
> Subject: Re: MXE: qt error with native build
>
> John D wrote:
> <snip>
>> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensou
>> r
>> ce-src
>> -4.8.3//projects.pro
>> -o Makefile -spec win32-g++
>> "make" -w -- JOBS=1 -f Makefile
>> make[3]: Entering directory
>> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
>> make[3]: *** No rule to make target `-f'.  Stop.
>> ------------------------------
>>
>> It does the same on mine
>> Running just normal 'make' to create octave works fine though
>
> Not here:
>
> :
> make[8]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src
> /plugi
> ns/imageformats/mng'
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src
> -4.8.3/bin/qmake
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src -4.8.3/src/plugins/imageformats/mng/mng.pro
>    -o Makefile -spec win32-g++
> Project ERROR: Package libmng not found
> make[8]: *** [all] Error 2
>
> Philip
>
> -----
>
>
> That's from running make from the mxe-octave root directory?

Of course.
It wasn't obvious to me from what other subdir I should run make.

I suppose ~/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3 ?
(just tried - see below)

<from your other email:>
 >
 > Have you set PKG_CONFIG_PATH to
 > `/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig  ?

No, but after checking I'll rather set it to:
/home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig


(Hmmmm just tried the above - I still get:

:
cd mng/ && make -f Makefile
make[3]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/src/plugins/imageformats/mng/mng.pro
  -o Makefile -spec win32-g++
'pkg-config' is not recognized as an internal or external command, operable
program or batch file.
Project ERROR: Package libmng not found
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
make[2]: *** [sub-mng-make_default] Error 2
make[2]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats'
make[1]: *** [sub-imageformats-make_default] Error 2
make[1]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns'
make: *** [sub-plugins-make_default-ordered] Error 2

 From where should I start over?

Thanks,

P.

-----


Check that mng was installed - installed-packages/libmng, and if it was:
export /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
make

(in the /home/Philip/mxe-octave) folder and see what happens.

Also, just for info, I created a script in tools/set_mxe_env.sh you can run
as source tools/set_mxe_env.sh, that sets all the bin/lib/config paths that
may help.
I created it for compiling the octave_hg versions of code in mingw after
having a working mxe-octave.
It isn't much use for anything except for native mingw builds.


Reply | Threaded
Open this post in threaded view
|

Re: MXE: qt error with native build

Michael Goffioul
On Thu, Jun 20, 2013 at 5:13 PM, John D <[hidden email]> wrote:


-----Original Message-----
From: Philip Nienhuis [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 4:56 PM
To: John D
Cc: [hidden email]
Subject: Re: MXE: qt error with native build

John D wrote:
>
>
> -----Original Message-----
> From: Philip Nienhuis [mailto:[hidden email]]
> Sent: Thursday, June 20, 2013 4:11 PM
> To: John D
> Cc: [hidden email]
> Subject: Re: MXE: qt error with native build
>
> John D wrote:
> <snip>
>> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensou
>> r
>> ce-src
>> -4.8.3//projects.pro
>> -o Makefile -spec win32-g++
>> "make" -w -- JOBS=1 -f Makefile
>> make[3]: Entering directory
>> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
>> make[3]: *** No rule to make target `-f'.  Stop.
>> ------------------------------
>>
>> It does the same on mine
>> Running just normal 'make' to create octave works fine though
>
> Not here:
>
> :
> make[8]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src
> /plugi
> ns/imageformats/mng'
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src
> -4.8.3/bin/qmake
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src -4.8.3/src/plugins/imageformats/mng/mng.pro
>    -o Makefile -spec win32-g++
> Project ERROR: Package libmng not found
> make[8]: *** [all] Error 2
>
> Philip
>
> -----
>
>
> That's from running make from the mxe-octave root directory?

Of course.
It wasn't obvious to me from what other subdir I should run make.

I suppose ~/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3 ?
(just tried - see below)

<from your other email:>
 >
 > Have you set PKG_CONFIG_PATH to
 > `/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig  ?

No, but after checking I'll rather set it to:
/home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig


(Hmmmm just tried the above - I still get:

:
cd mng/ && make -f Makefile
make[3]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/src/plugins/imageformats/mng/mng.pro
  -o Makefile -spec win32-g++
'pkg-config' is not recognized as an internal or external command, operable
program or batch file.
Project ERROR: Package libmng not found
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
make[2]: *** [sub-mng-make_default] Error 2
make[2]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats'
make[1]: *** [sub-imageformats-make_default] Error 2
make[1]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns'
make: *** [sub-plugins-make_default-ordered] Error 2

 From where should I start over?

Thanks,

P.

-----


Check that mng was installed - installed-packages/libmng, and if it was:
export /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
make

(in the /home/Philip/mxe-octave) folder and see what happens.

Also, just for info, I created a script in tools/set_mxe_env.sh you can run
as source tools/set_mxe_env.sh, that sets all the bin/lib/config paths that
may help.
I created it for compiling the octave_hg versions of code in mingw after
having a working mxe-octave.
It isn't much use for anything except for native mingw builds.

I only followed the discussion a little bit, but I've the impression these specific variables should be set by the top-level Makefile.

Michael.

Reply | Threaded
Open this post in threaded view
|

RE: MXE: qt error with native build

John Donoghue-3

 

 

From: Michael Goffioul [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 5:54 PM
To: John D
Cc: Philip Nienhuis; Octave Maintainers List
Subject: Re: MXE: qt error with native build

 

On Thu, Jun 20, 2013 at 5:13 PM, John D <[hidden email]> wrote:



-----Original Message-----
From: Philip Nienhuis [mailto:[hidden email]]
Sent: Thursday, June 20, 2013 4:56 PM
To: John D
Cc: [hidden email]
Subject: Re: MXE: qt error with native build

John D wrote:


>
>
> -----Original Message-----
> From: Philip Nienhuis [mailto:[hidden email]]
> Sent: Thursday, June 20, 2013 4:11 PM
> To: John D
> Cc: [hidden email]
> Subject: Re: MXE: qt error with native build
>
> John D wrote:
> <snip>
>> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensou
>> r
>> ce-src
>> -4.8.3//projects.pro
>> -o Makefile -spec win32-g++
>> "make" -w -- JOBS=1 -f Makefile
>> make[3]: Entering directory
>> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
>> make[3]: *** No rule to make target `-f'.  Stop.
>> ------------------------------
>>
>> It does the same on mine
>> Running just normal 'make' to create octave works fine though
>
> Not here:
>
> :
> make[8]: Entering directory
> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src
> /plugi
> ns/imageformats/mng'
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src
> -4.8.3/bin/qmake
> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
> ce-src -4.8.3/src/plugins/imageformats/mng/mng.pro
>    -o Makefile -spec win32-g++
> Project ERROR: Package libmng not found
> make[8]: *** [all] Error 2
>
> Philip
>
> -----
>
>
> That's from running make from the mxe-octave root directory?

Of course.
It wasn't obvious to me from what other subdir I should run make.

I suppose ~/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3 ?
(just tried - see below)

<from your other email:>
 >
 > Have you set PKG_CONFIG_PATH to
 > `/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig  ?

No, but after checking I'll rather set it to:
/home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig


(Hmmmm just tried the above - I still get:

:
cd mng/ && make -f Makefile
make[3]: Entering directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/bin/qmake
X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src
-4.8.3/src/plugins/imageformats/mng/mng.pro
  -o Makefile -spec win32-g++
'pkg-config' is not recognized as an internal or external command, operable
program or batch file.
Project ERROR: Package libmng not found
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats/mng'
make[2]: *** [sub-mng-make_default] Error 2
make[2]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns/imageformats'
make[1]: *** [sub-imageformats-make_default] Error 2
make[1]: Leaving directory
`/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src/plugi
ns'
make: *** [sub-plugins-make_default-ordered] Error 2

 From where should I start over?

Thanks,

P.

-----


Check that mng was installed - installed-packages/libmng, and if it was:
export /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
make

(in the /home/Philip/mxe-octave) folder and see what happens.

Also, just for info, I created a script in tools/set_mxe_env.sh you can run
as source tools/set_mxe_env.sh, that sets all the bin/lib/config paths that
may help.
I created it for compiling the octave_hg versions of code in mingw after
having a working mxe-octave.
It isn't much use for anything except for native mingw builds.

 

I only followed the discussion a little bit, but I've the impression these specific variables should be set by the top-level Makefile.

 

Michael.

 


 

They are(with the exception of PKG_CONFIG_PATH, which used to be there, but I believe no longer is)

My script is more for use with compiling the octave directly from the main hg repo than for compiling mxe-octave.

 

Reply | Threaded
Open this post in threaded view
|

Re: MXE: qt error with native build

PhilipNienhuis
John D wrote:

> *From:* Michael Goffioul [mailto:[hidden email]]
> *Sent:* Thursday, June 20, 2013 5:54 PM
> *To:* John D
> *Cc:* Philip Nienhuis; Octave Maintainers List
> *Subject:* Re: MXE: qt error with native build
>
> On Thu, Jun 20, 2013 at 5:13 PM, John D <[hidden email]
> <mailto:[hidden email]>> wrote:
>     -----Original Message-----
>     From: Philip Nienhuis [mailto:[hidden email]
>     John D wrote:
>      >
>      >
>      > -----Original Message-----
>      > From: Philip Nienhuis [mailto:[hidden email]
>     <mailto:[hidden email]>]
>      > Sent: Thursday, June 20, 2013 4:11 PM
>      > To: John D
>      > Cc: [hidden email]
>     <mailto:[hidden email]>
>      > Subject: Re: MXE: qt error with native build
>      >
>      > John D wrote:
>      > <snip>
>      >>
>     X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensou
>      >> r
>      >> ce-src
>      >> -4.8.3//projects.pro <http://projects.pro>
>      >> -o Makefile -spec win32-g++
>      >> "make" -w -- JOBS=1 -f Makefile
>      >> make[3]: Entering directory
>      >> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
>      >> make[3]: *** No rule to make target `-f'. Stop.
>      >> ------------------------------
>      >>
>      >> It does the same on mine
>      >> Running just normal 'make' to create octave works fine though
>      >
>      > Not here:
>      >
>      > :
>      > make[8]: Entering directory
>      >
>     `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src
>      > /plugi
>      > ns/imageformats/mng'
>      >
>     X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
>      > ce-src
>      > -4.8.3/bin/qmake
>      >
>     X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
>      > ce-src -4.8.3/src/plugins/imageformats/mng/mng.pro <http://mng.pro>
>      > -o Makefile -spec win32-g++
>      > Project ERROR: Package libmng not found
>      > make[8]: *** [all] Error 2
>      >

:<snip>
<John D:>

>      > That's from running make from the mxe-octave root directory?
>
>     Of course.
>     It wasn't obvious to me from what other subdir I should run make.
>
>     I suppose ~/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3 ?
>     (just tried - see below)
>
>     <from your other email:>
>      >
>      > Have you set PKG_CONFIG_PATH to
>      > `/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig ?
>
>     No, but after checking I'll rather set it to:
>     /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
:
<snip>
<John D:>

>     Check that mng was installed - installed-packages/libmng, and if it was:
>     export /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
>     make
>
>     (in the /home/Philip/mxe-octave) folder and see what happens.
>
>     Also, just for info, I created a script in tools/set_mxe_env.sh you
>     can run
>     as source tools/set_mxe_env.sh, that sets all the bin/lib/config
>     paths that
>     may help.
>     I created it for compiling the octave_hg versions of code in mingw after
>     having a working mxe-octave.
>     It isn't much use for anything except for native mingw builds.
>
> I only followed the discussion a little bit, but I've the impression
> these specific variables should be set by the top-level Makefile.
>
> Michael.
>
> ------------------------------------------------------------------------
>
> They are(with the exception of PKG_CONFIG_PATH, which used to be there,
> but I believe no longer is)
>
> My script is more for use with compiling the octave directly from the
> main hg repo than for compiling mxe-octave.

After properly setting PKG_CONFIG_PATH and restarting "make" in
./mxe-octave top dir, I found that the build got as far as octave itself.
It stopped with "no space left on device" but that is obviously my side
of things. (Good to know that this joke needs some 2.5 - 3 GB disk space
all together)
Another 2-3 hour wait I suppose.....

Philip
Reply | Threaded
Open this post in threaded view
|

Fixed [Re: MXE: qt error with native build]

PhilipNienhuis
Philip Nienhuis wrote:

> John D wrote:
>> *From:* Michael Goffioul [mailto:[hidden email]]
>> *Sent:* Thursday, June 20, 2013 5:54 PM
>> *To:* John D
>> *Cc:* Philip Nienhuis; Octave Maintainers List
>> *Subject:* Re: MXE: qt error with native build
>>
>> On Thu, Jun 20, 2013 at 5:13 PM, John D <[hidden email]
>> <mailto:[hidden email]>> wrote:
>> -----Original Message-----
>> From: Philip Nienhuis [mailto:[hidden email]
>> John D wrote:
>> >
>> >
>> > -----Original Message-----
>> > From: Philip Nienhuis [mailto:[hidden email]
>> <mailto:[hidden email]>]
>> > Sent: Thursday, June 20, 2013 4:11 PM
>> > To: John D
>> > Cc: [hidden email]
>> <mailto:[hidden email]>
>> > Subject: Re: MXE: qt error with native build
>> >
>> > John D wrote:
>> > <snip>
>> >>
>> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensou
>> >> r
>> >> ce-src
>> >> -4.8.3//projects.pro <http://projects.pro>
>> >> -o Makefile -spec win32-g++
>> >> "make" -w -- JOBS=1 -f Makefile
>> >> make[3]: Entering directory
>> >> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3'
>> >> make[3]: *** No rule to make target `-f'. Stop.
>> >> ------------------------------
>> >>
>> >> It does the same on mine
>> >> Running just normal 'make' to create octave works fine though
>> >
>> > Not here:
>> >
>> > :
>> > make[8]: Entering directory
>> >
>> `/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3/src
>> > /plugi
>> > ns/imageformats/mng'
>> >
>> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
>> > ce-src
>> > -4.8.3/bin/qmake
>> >
>> X:/MinGW/msys/1.0/home/Philip/mxe-octave/tmp-qt/qt-everywhere-opensour
>> > ce-src -4.8.3/src/plugins/imageformats/mng/mng.pro <http://mng.pro>
>> > -o Makefile -spec win32-g++
>> > Project ERROR: Package libmng not found
>> > make[8]: *** [all] Error 2
>> >
>
> :<snip>
> <John D:>
>> > That's from running make from the mxe-octave root directory?
>>
>> Of course.
>> It wasn't obvious to me from what other subdir I should run make.
>>
>> I suppose ~/mxe-octave/tmp-qt/qt-everywhere-opensource-src-4.8.3 ?
>> (just tried - see below)
>>
>> <from your other email:>
>> >
>> > Have you set PKG_CONFIG_PATH to
>> > `/home/Philip/mxe-octave/usr/i686-pc-mingw/lib/pkgconfig ?
>>
>> No, but after checking I'll rather set it to:
>> /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
> :
> <snip>
> <John D:>
>> Check that mng was installed - installed-packages/libmng, and if it was:
>> export /home/Philip/mxe-octave/usr/i686-pc-mingw32/lib/pkgconfig
>> make
>>
>> (in the /home/Philip/mxe-octave) folder and see what happens.
>>
>> Also, just for info, I created a script in tools/set_mxe_env.sh you
>> can run
>> as source tools/set_mxe_env.sh, that sets all the bin/lib/config
>> paths that
>> may help.
>> I created it for compiling the octave_hg versions of code in mingw after
>> having a working mxe-octave.
>> It isn't much use for anything except for native mingw builds.
>>
>> I only followed the discussion a little bit, but I've the impression
>> these specific variables should be set by the top-level Makefile.
>>
>> Michael.
>>
>> ------------------------------------------------------------------------
>>
>> They are(with the exception of PKG_CONFIG_PATH, which used to be there,
>> but I believe no longer is)
>>
>> My script is more for use with compiling the octave directly from the
>> main hg repo than for compiling mxe-octave.
>
> After properly setting PKG_CONFIG_PATH and restarting "make" in
> ./mxe-octave top dir, I found that the build got as far as octave itself.
> It stopped with "no space left on device" but that is obviously my side
> of things. (Good to know that this joke needs some 2.5 - 3 GB disk space
> all together)
> Another 2-3 hour wait I suppose.....

Well that wasn't too bad: just 1.5 hours to build Octave.

After adding /home/Philip/mxe-octave/usr/i686-pc-mingw32/bin to the PATH
I can now run Octave. Neat!


Of course there are some remaining things:

- Octave starts off with a "-K>>" prompt (JD I think you mentioned this)
and no blinking cursor (bug #39259)

- Continuing the setup of the dist subdir (mk-dist ...) fails with
"make: *** No rule to make target
`/home/Philip/mxe-octave/installed-packages/build-binutils', needed  by
`/home/Philip/mxe-octave/installed-packages/native-gcc'.  Stop."


- My own aim was not so much being able to build an Octave binary
distribution natively on Windows (would be nice though), but first of
all to get at a point where I could "hg clone" the Octave dev version,
build it (optionally with --enable-debug) and run "make check", all
meant to make debugging on MinGW less involved.

John D, did I read you correctly that:
> Also, just for info, I created a script in tools/set_mxe_env.sh you can run as source tools/set_mxe_env.sh, that sets all the bin/lib/config paths that may help.
> I created it for compiling the octave_hg versions of code in mingw after
> having a working mxe-octave.
> It isn't much use for anything except for native mingw builds.
... that script is meant to aid exactly that purpose?


- JWE/John D, I documented all steps I took to get a working mxe-built
Octave. Given your remarks in recent postings:
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2013-June/034313.html 
  (and follow-up)
would you mind if I put it up on the wiki? or shall I just post it here
on the maintainers ML?

Philip
Reply | Threaded
Open this post in threaded view
|

RE: Fixed [Re: MXE: qt error with native build]

John Donoghue-3


-----Original Message-----
From: Philip Nienhuis [mailto:[hidden email]]
Sent: Friday, June 21, 2013 4:56 AM
To: John D
Cc: 'Octave Maintainers List'; [hidden email]
Subject: Fixed [Re: MXE: qt error with native build]

<snip>
- My own aim was not so much being able to build an Octave binary
distribution natively on Windows (would be nice though), but first of
all to get at a point where I could "hg clone" the Octave dev version,
build it (optionally with --enable-debug) and run "make check", all
meant to make debugging on MinGW less involved.

John D, did I read you correctly that:
> Also, just for info, I created a script in tools/set_mxe_env.sh you can
run as source tools/set_mxe_env.sh, that sets all the bin/lib/config paths
that may help.
> I created it for compiling the octave_hg versions of code in mingw after
> having a working mxe-octave.
> It isn't much use for anything except for native mingw builds.
... that script is meant to aid exactly that purpose?


- JWE/John D, I documented all steps I took to get a working mxe-built
Octave. Given your remarks in recent postings:
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2013-June/034313.h
tml
  (and follow-up)
would you mind if I put it up on the wiki? or shall I just post it here
on the maintainers ML?

Philip

-----

Yes the script is for that - I have successfully built octave checked out
from octave hg a few times now.
All you need to do is check out the sources, source the set_mxe_env.sh
script, and then run run bootstrap, configure, make like you normally would
have to on a unix system.

It will build octave, but fail at generating all the documentation, but the
./run-octave script in the build directory will run the latest and greatest
from the octave hg repo!


Reply | Threaded
Open this post in threaded view
|

Re: Fixed [Re: MXE: qt error with native build]

Michael Goffioul
In reply to this post by PhilipNienhuis
On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis <[hidden email]> wrote:
Of course there are some remaining things:

- Octave starts off with a "-K>>" prompt (JD I think you mentioned this) and no blinking cursor (bug #39259)

Do you start octave from the MSYS shell?
If you do, try to unset TERM variable, like: TERM= octave.exe

Michael.

Reply | Threaded
Open this post in threaded view
|

RE: Fixed [Re: MXE: qt error with native build]

John Donoghue-3

 

 

From: Michael Goffioul [mailto:[hidden email]]
Sent: Friday, June 21, 2013 6:44 AM
To: Philip Nienhuis
Cc: John D; John W. Eaton; Octave Maintainers List
Subject: Re: Fixed [Re: MXE: qt error with native build]

 

On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis <[hidden email]> wrote:

Of course there are some remaining things:

- Octave starts off with a "-K>>" prompt (JD I think you mentioned this) and no blinking cursor (bug #39259)

 

Do you start octave from the MSYS shell?

If you do, try to unset TERM variable, like: TERM= octave.exe

 

Michael.

 

 

Unsetting term works for me

Reply | Threaded
Open this post in threaded view
|

Re: Fixed [Re: MXE: qt error with native build]

Michael Goffioul
On Fri, Jun 21, 2013 at 6:53 AM, John D <[hidden email]> wrote:

 

 

From: Michael Goffioul [mailto:[hidden email]]
Sent: Friday, June 21, 2013 6:44 AM
To: Philip Nienhuis
Cc: John D; John W. Eaton; Octave Maintainers List
Subject: Re: Fixed [Re: MXE: qt error with native build]

 

On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis <[hidden email]> wrote:

Of course there are some remaining things:

- Octave starts off with a "-K>>" prompt (JD I think you mentioned this) and no blinking cursor (bug #39259)

 

Do you start octave from the MSYS shell?

If you do, try to unset TERM variable, like: TERM= octave.exe

 

Michael.

 

 

Unsetting term works for me


The problem is that octave inherits TERM from the shell, I think it's set to something like cygwin or rxvt (I don't remember). And readline then starts sending control sequences that are not understood by the windows terminal.

Michael.

Reply | Threaded
Open this post in threaded view
|

RE: Fixed [Re: MXE: qt error with native build]

John Donoghue-3

 

 

From: Michael Goffioul [mailto:[hidden email]]
Sent: Friday, June 21, 2013 6:57 AM
To: John D
Cc: Philip Nienhuis; John W. Eaton; Octave Maintainers List
Subject: Re: Fixed [Re: MXE: qt error with native build]

 

On Fri, Jun 21, 2013 at 6:53 AM, John D <[hidden email]> wrote:

 

 

From: Michael Goffioul [mailto:[hidden email]]
Sent: Friday, June 21, 2013 6:44 AM
To: Philip Nienhuis
Cc: John D; John W. Eaton; Octave Maintainers List
Subject: Re: Fixed [Re: MXE: qt error with native build]

 

On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis <[hidden email]> wrote:

Of course there are some remaining things:

- Octave starts off with a "-K>>" prompt (JD I think you mentioned this) and no blinking cursor (bug #39259)

 

Do you start octave from the MSYS shell?

If you do, try to unset TERM variable, like: TERM= octave.exe

 

Michael.

 

 

Unsetting term works for me

 

The problem is that octave inherits TERM from the shell, I think it's set to something like cygwin or rxvt (I don't remember). And readline then starts sending control sequences that are not understood by the windows terminal.

 

Michael.

 

 

Make sense to me and I should have realized that was the issue J

 

On mine:

$ echo $TERM

cygwin

 

Reply | Threaded
Open this post in threaded view
|

Re: Fixed [Re: MXE: qt error with native build]

PhilipNienhuis
In reply to this post by Michael Goffioul
Michael Goffioul wrote:

> On Fri, Jun 21, 2013 at 6:53 AM, John D <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     __ __
>
>     __ __
>
>     *From:* Michael Goffioul [mailto:[hidden email]
>     <mailto:[hidden email]>]
>     *Sent:* Friday, June 21, 2013 6:44 AM
>     *To:* Philip Nienhuis
>     *Cc:* John D; John W. Eaton; Octave Maintainers List
>     *Subject:* Re: Fixed [Re: MXE: qt error with native build]____
>     On Fri, Jun 21, 2013 at 4:56 AM, Philip Nienhuis
>     <[hidden email] <mailto:[hidden email]>> wrote:____
>
>         Of course there are some remaining things:
>
>         - Octave starts off with a "-K>>" prompt (JD I think you
>         mentioned this) and no blinking cursor (bug #39259)____
>
>     Do you start octave from the MSYS shell?____
>
>     If you do, try to unset TERM variable, like: TERM= octave.exe
<JD:>
>>
>>     Unsetting term works for me____
>
> The problem is that octave inherits TERM from the shell, I think it's
> set to something like cygwin or rxvt (I don't remember). And readline
> then starts sending control sequences that are not understood by the
> windows terminal.

The -[K>> prompt doesn't appear in octave-cli. It's only an issue in the
GUI command window (and only before the first command is entered.)

Does that still fit the picture?

Philip
12