From: Chris S. <iro...@ro...> - 2003-07-10 23:16:21
|
Hey, Nice work on the 1.0.9 release! I've just noticed a little thing, namely, the ftp is starting in it's own cmd window again (used to, then it was fixed). I've done a 'which ftp' and it is indeed the msys one. Anybody have any ideas? Well I'm at it... I was thinking of grabbing the msysDTK source and taking a look at the telnet code. I'd like to get the emulation to work a little better with Solaris machines (currently it behaves oddly with vi, even with TERM set to vt100). Cheers! Chris --- iro...@ro... http://ishell.sourceforge.net http://shellwm.sourceforge.net http://bb4win.org |
From: Earnie B. <ear...@ya...> - 2003-07-11 01:06:39
|
Chris Sutcliffe wrote: > Hey, > > Nice work on the 1.0.9 release! I've just noticed a little thing, > namely, the ftp is starting in it's own cmd window again (used to, then > it was fixed). I've done a 'which ftp' and it is indeed the msys one. > > Anybody have any ideas? > Did you allow the postinstall to run? If you have /bin/ftp.exe the postinstall would have removed the /bin/ftp script. > Well I'm at it... I was thinking of grabbing the msysDTK source and > taking a look at the telnet code. I'd like to get the emulation to work > a little better with Solaris machines (currently it behaves oddly with > vi, even with TERM set to vt100). > It's not particularly the telnet code itself that is the problem. It is the vt100 emulation work in MSYS itself. A helping hand would be appreciated with that. The MSYS runtime resides in CVS at ``cvs -d:pserver:an...@cv...:/src/mingw co msys/rt''. The msysDTK-src package contains the inet utilities that contains telnet. You will need the msysDVLPR package to build msys dependent binaries. Earnie. |
From: Chris S. <iro...@ro...> - 2003-07-12 01:27:37
|
Me again, > Did you allow the postinstall to run? If you have /bin/ftp.exe the > postinstall would have removed the /bin/ftp script. Removed the /bin/ftp script now everything works like a charm... thanx! > It's not particularly the telnet code itself that is the problem. It > is the vt100 emulation work in MSYS itself. A helping hand would be > appreciated with that. The MSYS runtime resides in CVS at ``cvs > -d:pserver:an...@cv...:/src/mingw co msys/rt''. The > msysDTK-src package contains the inet utilities that contains telnet. > You will need the msysDVLPR package to build msys dependent binaries. I'm running the msysDTK 1.0.1, and on the site, all I can find is msysDVLPR 1.0.0, does it matter? If so, is there an update I can grab from somewhere? I'll grab the CVS and start taking a look. Cheers! Chris |
From: Earnie B. <ear...@ya...> - 2003-07-12 12:47:08
|
Chris Sutcliffe wrote: > > I'm running the msysDTK 1.0.1, and on the site, all I can find is > msysDVLPR 1.0.0, does it matter? If so, is there an update I can grab > from somewhere? I'll grab the CVS and start taking a look. > That's it! You've found it. I'll be updating it soon with a newer version of GCC for MSYS. Be sure to use the msysdvlpr command to open an MSYS window. Earnie. |
From: Chris S. <iro...@ro...> - 2003-07-12 19:12:29
|
Hey, > I'll be updating it soon with a newer version of GCC for MSYS. Be > sure to use the msysdvlpr command to open an MSYS window. Sounds sweet. I've got a 'msysdvlpr' command window open. When I do a 'configure' followed by 'make', I get the following errors: pexecute.c: In function `pexecute': pexecute.c:378: warning: implicit declaration of function `_pipe' pexecute.c:408: `_spawnvp' undeclared (first use in this function) pexecute.c:408: (Each undeclared identifier is reported only once pexecute.c:408: for each function it appears in.) pexecute.c:408: `_spawnv' undeclared (first use in this function) pexecute.c:426: warning: assignment discards qualifiers from pointer target type pexecute.c:361: warning: unused variable `retries' pexecute.c:361: warning: unused variable `sleep_interval' pexecute.c:353: warning: unused parameter `this_pname' pexecute.c:354: warning: unused parameter `temp_base' pexecute.c: In function `pwait': pexecute.c:451: warning: implicit declaration of function `_cwait' pexecute.c:444: warning: unused parameter `flags' make[1]: *** [pexecute.o] Error 1 make[1]: Leaving directory `/development/msys/rt/src/i686-pc-msys/libiberty' make: *** [all-target-libiberty] Error 2 Do you have any idea what I'm doing wrong? FYI, my path is the following: $ echo $PATH .:/usr/local/bin:/bin:/mingw/bin:.:/local/bin:/mingw/bin:/usr/bin:/c/j2sdk/bin:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/system32/Wbem I have the 'msysdvlpr' package in '/MSYS-dev'. Thanx! Chris |
From: Earnie B. <ear...@ya...> - 2003-07-13 06:55:22
|
Chris Sutcliffe wrote: > > > I have the 'msysdvlpr' package in '/MSYS-dev'. > Move it to /. It belongs in the root of MSYS. Earnie. |
From: Chris S. <iro...@ro...> - 2003-07-13 14:15:16
|
I'm getting there.... I moved the msysdvlr package to the root directory of msys. I did the 'configure' / 'make' combo, and then I got the following: configuring in cygwin running /bin/sh ./configure --host=i686-pc-msys --build=i686-pc-msys --with-newlib --enable-multilib --with-target-subdir=i686-pc-msys --cache-file=../../config.cache --srcdir=. loading cache ../../config.cache configure: error: can not find install-sh or install.sh in . ./.. ./../.. configure: error: ./configure failed for cygwin make[1]: Entering directory `/development/msys/rt/src/i686-pc-msys/winsup' make[2]: Entering directory `/development/msys/rt/src/i686-pc-msys/winsup/cygwin' make[2]: *** No rule to make target `all'. Stop. make[2]: Leaving directory `/development/msys/rt/src/i686-pc-msys/winsup/cygwin' make[1]: *** [cygwin] Error 2 make[1]: Leaving directory `/development/msys/rt/src/i686-pc-msys/winsup' make: *** [all-target-winsup] Error 2 so I linked install-sh in rt/src to the rt/src/i686-pc-msys directory. I then hit the following: make[1]: Entering directory `/development/msys/rt/src/i686-pc-msys/winsup' make[2]: Entering directory `/development/msys/rt/src/i686-pc-msys/winsup/cygwin' make[2]: *** No rule to make target `clean'. Stop. make[2]: Leaving directory `/development/msys/rt/src/i686-pc-msys/winsup/cygwin' make[1]: *** [clean_cygwin] Error 2 make[1]: Leaving directory `/development/msys/rt/src/i686-pc-msys/winsup' make: *** [do-clean] Error 1 So I ran 'configure' manually, and found: loading cache ./config.cache checking for a BSD compatible install... /bin/install -c configure: error: can not run ./../../config.sub So I linked config.guess and config.sub from rt/src to rt/src/i686-pc-msys. After all that I get: In file included from cygheap.cc:17: fhandler.h: In method `select_stuff::select_stuff()': fhandler.h:1067: implicit declaration of function `int memset(...)' make[2]: *** [cygheap.o] Error 1 make[2]: Leaving directory `/development/msys/rt/src/i686-pc-msys/winsup/cygwin' make[1]: *** [cygwin] Error 2 make[1]: Leaving directory `/development/msys/rt/src/i686-pc-msys/winsup' make: *** [all-target-winsup] Error 2 Should I modify the source, or am I missing something? Cheers! Chris |
From: Earnie B. <ear...@ya...> - 2003-07-13 18:55:45
|
Chris Sutcliffe wrote: > I'm getting there.... I moved the msysdvlr package to the root > directory of msys. I did the 'configure' / 'make' combo, and then I got > the following: > > configuring in cygwin > running /bin/sh ./configure --host=i686-pc-msys --build=i686-pc-msys > --with-newlib --enable-multilib --with-target-subdir=i686-pc-msys > --cache-file=../../config.cache --srcdir=. You need to configure in a build directory, not the source directory. E.G.: cd msys/rt && mkdir bld && cd bld && ../src/configure --prefix=/usr > > Should I modify the source, or am I missing something? > No, you shouldn't need to modify anything, if you have you may need to undo what you've done. Note that the top_level configure script is not an autoconf generated script. It was home brewed by what used to be Cygnus Corp. now a part of Redhat. Earnie. |
From: Chris S. <iro...@ro...> - 2003-07-14 14:48:51
|
I've gotten a little furter... > You need to configure in a build directory, not the source directory. > E.G.: cd msys/rt && mkdir bld && cd bld && ../src/configure --prefix=/usr As per your instruction, I nuked my exist msys/rt dir, and grabbed it again from CVS. After that I created a msys/rt/build directory, and did exactly what you mentioned. I then got the following during the compile process: c++ -L/development/msys/rt/build/i686-pc-msys/winsup -L/development/msys/rt/build/i686-pc-msys/winsup/cygwin -isystem /development/msys/rt/src/winsup/include -isystem /development/msys/rt/src/winsup/cygwin/include -isystem /development/msys/rt/src/newlib/libc/sys/cygwin -isystem /development/msys/rt/src/newlib/libc/sys/cygwin32 -B/development/msys/rt/build/i686-pc-msys/newlib/ -isystem /development/msys/rt/build/i686-pc-msys/newlib/targ-include -isystem /development/msys/rt/src/newlib/libc/include -c -nostdinc++ -DHAVE_CONFIG_H -g -O2 -Wall -Wwrite-strings -I. -I/development/msys/rt/src/winsup/cygwin/include -I/development/msys/rt/src/winsup/cygwin -I/development/msys/rt/src/newlib/libc/sys/cygwin -I/development/msys/rt/src/newlib/libc/include -I/development/msys/rt/src/winsup/w32api/include -I../../../../src/winsup/cygwin/config/i386 -I/bin/../lib/gcc-lib/i686-pc-msys/2.95.3-1//include -I/usr/include/c++/3.2.2 -I/usr/include/c++/3.2.2/i686-pc-msys -fno-rtti -fno-exceptions -o ./tty.o ../../../../src/winsup/cygwin/tty.cc ../../../../src/winsup/cygwin/tty.cc: In method `int tty_list::allocate_tty(int)': ../../../../src/winsup/cygwin/tty.cc:214: implicit declaration of function `int GetConsoleWindow(...)' ../../../../src/winsup/cygwin/tty.cc:214: assignment to `HWND__ *' from `int' lacks a cast make[2]: *** [tty.o] Error 1 make[2]: Leaving directory `/development/msys/rt/build/i686-pc-msys/winsup/cygwin' make[1]: *** [cygwin] Error 2 make[1]: Leaving directory `/development/msys/rt/build/i686-pc-msys/winsup' make: *** [all-target-winsup] Error 2 Did I miss something else? Cheers! Chris |
From: Earnie B. <ear...@ya...> - 2003-07-15 00:03:07
|
Chris Sutcliffe wrote: > > Did I miss something else? > No. I did. Put a copy of the w32api/include directory under the winsup src. The directory structure must be winsup/w32api/include and only the w32api files not the headers from the mingw-runtime. Earnie. |