From: Lennart B. <len...@st...> - 2005-09-27 14:24:31
|
Earnie Boyd wrote: > Quoting Lennart Borgman <len...@st...>: > >> Lennart Borgman wrote: >> >>> Keith MARSHALL wrote: >>> >>>> Lennart Borgman wrote, quoting me: >>>> >>>>>> Are you running in the MSYS developer environment? >>>>> >>>>> >>>>> Yes, I think so. I have installed msysDTK-1.0.1.exe. >>>>> >>>> >>>> >>>> That's not what you need. You need msysDVLPR. >>>> >>> Thanks Keith, I just downloaded msysDVLPR and had a look. It looks >>> like a totally new building environment. I am very sure I do not >>> understand everything here. Why can't this be built with MinGW? Why >>> are not the needed header files either in MinGW or in the MSYS CVS? >> >> >> With the help of your hint about msysDVLPR I found the page >> http://www.mingw.org/MinGWiki/index.php/Build%20MSYS and followed the >> instructions there. The build process ran well until I got this: >> >> make[2]: Entering directory >> `/d/mingwcvs/msys/rt/bld/i686-pc-msys/winsup/cygwin' >> make[2]: *** No rule to make target `all'. Stop. >> make[2]: Leaving directory >> `/d/mingwcvs/msys/rt/bld/i686-pc-msys/winsup/cygwin' >> make[1]: *** [cygwin] Error 2 >> make[1]: Leaving directory >> `/d/mingwcvs/msys/rt/bld/i686-pc-msys/winsup' >> make: *** [all-target-winsup] Error 2 >> >> Anyway this is not really what I want to do. I would like to build >> just bash as a standalone app. The sources for bash in MSYS CVS are >> of course not for this, but if I want to do that I hoped that they >> would be a good starting point. Are they really a good starting point >> for that or? >> > > Although you don't wish to build MSYS it should help you build > applications that > are dependent on the MSYS runtime. You need to configure bash while > uname > reports a system of MSYS instead of MINGW32. And you need to have > msysDVLPR in > place for the runtime libraries. > > Earnie Making a directory parallell to bash\2.05b and running ../2.05b/configure there I ran into the usual problem with unix line endings on ms windows in the .def-files. (Getting rid of that is one reason I am doing this.) Fixing this and running make again I get the following error: gcc -DPROGRAM='"bash.exe"' -DCONF_HOSTTYPE='"i686"' -DCONF_OSTYPE='"msys"' -DCONF_MACHTYPE='"i686-pc-msys"' -DCONF_VENDOR='"pc"' -DSHELL -DHAVE_CONFIG_H -I. -I../2.05b -I../2.05b/include -I../2.05b/lib -g -O2 -c ../2.05b/jobs.c In file included from ../2.05b/jobs.c:52: ../2.05b/include/shtty.h:61: sgtty.h: No such file or directory make: *** [jobs.o] Error 1 |