From: Brian K. <bk...@on...> - 2002-02-20 13:50:19
|
Here is a different, but related question... I took cygwin out of my Path variable (winXP) I don't think I'll need it anymore anyway. But now when I try to configure, it gets to the point where it looks for gcc's ld and can't find it. It finds the other pieces before that so I wonder what gives?? It says it can't find ld on the path. Is there a path to set in msys that is separate from the external path?? BTW thanks for your prompt responses!!! Brian Kropf -----Original Message----- From: min...@li... [mailto:min...@li...] On Behalf Of Earnie Boyd Sent: Wednesday, February 20, 2002 7:26 AM To: Earnie Boyd Cc: Brian Kropf; mingw users Subject: Re: [Mingw-msys] Re: [Mingw-users] Question about aclocal Earnie Boyd wrote: > > > Ok, I just tried this. It configures fine. Make sure that Cygwin isn't > in your PATH. The make stopped though on a windres error but that's a > different story. > Alright, the sigc++/sigc_res.rc file is empty from the distribution for some reason. I was able to complete the build by removing the requirement of sigc_res.rc from the sigc++/Makefile. I don't know what affect this may have. Do you have a valid sigc_res.rc file? Earnie. P.S.: One other thing I had to do was to `cd /mingw/lib && cp libstdc++.a.2.10.0 libstdc++.a'. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ MinGW-users mailing list Min...@li... You may change your MinGW Account Options or unsubscribe at: https://lists.sourceforge.net/lists/listinfo/mingw-users |
From: Brian K. <bk...@on...> - 2002-02-21 04:38:13
|
OK, I'm still having trouble, I think I've narrowed it down, but I don't know whether it is from the libsig configure or from my system. It is still giving me errors when I try configuring, and it is still at the ld portion of things. Here is the question: When I just type in gcc I get output like this: gcc.exe: No input files When I type in ld I get: c:\compilers\mingw\bin\ld.exe: No input files I have mingw installed (as you may have guessed) in c:\compilers\mingw Cygwin doesn't evince this when I tried the same steps. Does this happen with anyone else? I think that the configure script is expecting to find ld.exe but it is finding a full path returned to it. Btw. I can configure it with cygwin, since it isn't acting strangely with ld.exe -----Original Message----- From: Earnie Boyd [mailto:ear...@ya...] Sent: Wednesday, February 20, 2002 9:07 AM To: Brian Kropf Cc: 'Earnie Boyd' Subject: Re: [Mingw-msys] Re: [Mingw-users] Question about aclocal Brian Kropf wrote: > > Here is a different, but related question... > > I took cygwin out of my Path variable (winXP) I don't think I'll need it > anymore anyway. But now when I try to configure, it gets to the point > where it looks for gcc's ld and can't find it. It finds the other > pieces before that so I wonder what gives?? It says it can't find ld on > the path. Is there a path to set in msys that is separate from the > external path?? > My PATH is set to: /bin:/mingw/bin:/c/IT_Comm/Oracle/Net/bin:/c/WINNT/system32:/c/WINNT:/c/ WINNT/System32/WBEM I have MinGW-1.1 installed in C:\mingw and my /etc/fstab file contains: $ cat /etc/fstab c:/mingw /mingw > BTW thanks for your prompt responses!!! > Wednesday is my play day. ;) I hope to have MSYS-1.0.5 uploaded by the end of my day. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Earnie B. <ear...@ya...> - 2002-02-21 12:45:17
|
Brian Kropf wrote: > > OK, > I'm still having trouble, I think I've narrowed it down, but I don't > know whether it is from the libsig configure or from my system. It is > still giving me errors when I try configuring, and it is still at the ld > portion of things. > > Here is the question: > > When I just type in gcc I get output like this: gcc.exe: No input files > When I type in ld I get: c:\compilers\mingw\bin\ld.exe: No input files > Hmm... Does this work in a "MSDOS" Command window? Are you using MinGW-1.1? > I have mingw installed (as you may have guessed) in c:\compilers\mingw > What do you mean exactly? Is it c:\compilers\mingw\msys\1.0 or did you move the contents of the MSYS package? > Cygwin doesn't evince this when I tried the same steps. Does this > happen with anyone else? I think that the configure script is expecting > to find ld.exe but it is finding a full path returned to it. > > Btw. I can configure it with cygwin, since it isn't acting strangely > with ld.exe > Using the Makefile and config.h from a configure from under Cygwin would be wrong for MinGW. If you can't even get a configure to execute then I have to look at your MinGW environment. But let's take it a step at a time. Answer the above questions first. Eanrie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Brian K. <bk...@on...> - 2002-02-21 23:14:11
|
I suppose I should give a bit more information about how things are set up: Output from gcc -v: Reading specs from c:/compilers/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-5/specs gcc version 2.95.3-5 (mingw special) I have msys 1.04 with echo and the recent added package I have msys installed at: c:/compilers/msys(/1.0/bin ...) I have mingw installed at: c:/compilers/mingw(/bin ...) I have in my system path (amongst many other items): c:\compilers\mingw\bin When I type ld at the dos shell I get: ld.exe: no input files When I type ld at the msys shell I get: c:\compilers\mingw\bin\ld.exe: no input files I've even tried copying the entire mingw folder to under the 1.0 directory in msys, removing any system path pointers to the original mingw directory, and just using the msys path pointer to gcc. I still get the full path prepended to ld, but no other programs. Does this help at all?? > -----Original Message----- > From: Earnie Boyd [mailto:ear...@ya...] > Sent: Thursday, February 21, 2002 7:44 AM > To: Brian Kropf > Cc: mingw msys; lib...@li... > Subject: Re: [Mingw-msys] Re: [Mingw-users] Question about aclocal > > Brian Kropf wrote: > > > > OK, > > I'm still having trouble, I think I've narrowed it down, but I don't > > know whether it is from the libsig configure or from my system. It is > > still giving me errors when I try configuring, and it is still at the ld > > portion of things. > > > > Here is the question: > > > > When I just type in gcc I get output like this: gcc.exe: No input files > > When I type in ld I get: c:\compilers\mingw\bin\ld.exe: No input files > > > > Hmm... Does this work in a "MSDOS" Command window? > > Are you using MinGW-1.1? > > > I have mingw installed (as you may have guessed) in c:\compilers\mingw > > > > What do you mean exactly? Is it c:\compilers\mingw\msys\1.0 or did you > move the contents of the MSYS package? > > > Cygwin doesn't evince this when I tried the same steps. Does this > > happen with anyone else? I think that the configure script is expecting > > to find ld.exe but it is finding a full path returned to it. > > > > Btw. I can configure it with cygwin, since it isn't acting strangely > > with ld.exe > > > > Using the Makefile and config.h from a configure from under Cygwin would > be wrong for MinGW. If you can't even get a configure to execute then I > have to look at your MinGW environment. But let's take it a step at a > time. Answer the above questions first. > > Eanrie. > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > |
From: Earnie B. <ear...@ya...> - 2002-02-21 23:50:32
|
Brian Kropf wrote: > > I suppose I should give a bit more information about how things are set > up: > > Output from gcc -v: > Reading specs from > c:/compilers/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-5/specs > gcc version 2.95.3-5 (mingw special) > > I have msys 1.04 with echo and the recent added package > > I have msys installed at: c:/compilers/msys(/1.0/bin ...) > I have mingw installed at: c:/compilers/mingw(/bin ...) > > I have in my system path (amongst many other items): > c:\compilers\mingw\bin > > When I type ld at the dos shell I get: > ld.exe: no input files > > When I type ld at the msys shell I get: > c:\compilers\mingw\bin\ld.exe: no input files > So MSYS finds ld.exe just fine. Why doesn't the configure script? > I've even tried copying the entire mingw folder to under the 1.0 > directory in msys, removing any system path pointers to the original > mingw directory, and just using the msys path pointer to gcc. I still > get the full path prepended to ld, but no other programs. > That's because the full path is given to ld in argv[0] and it's programmed to use what ever argv[0] has for the name it prints. The others obviously just care about the basename. > Does this help at all?? > No, not really. What package are you building? Sorry if you've given this before. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Brian K. <bk...@on...> - 2002-02-22 01:35:46
|
I've been trying to build libsigc++ This is the output I get from running configure $ ./configure loading cache ./config.cache checking for a BSD compatible install... /bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... no checking for working aclocal... missing checking for working autoconf... missing checking for working automake... missing checking for working autoheader... missing checking for working makeinfo... found checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking how to run the C preprocessor... gcc -E checking host system type... i686-pc-mingw32 checking build system type... i686-pc-mingw32 checking for ranlib... ranlib checking for ld used by GCC... no configure: error: no acceptable ld found in $PATH The only thing I can think of for it not returning an "acceptable" ld is that the configure script is looking for ld.exe and not /c:/compilers/mingw/bin/ld.exe > -----Original Message----- > From: Earnie Boyd [mailto:ear...@ya...] > Sent: Thursday, February 21, 2002 6:49 PM > To: Brian Kropf > Cc: mingw msys > Subject: Re: [Mingw-msys] Re: [Mingw-users] Question about aclocal > > Brian Kropf wrote: > > > > I suppose I should give a bit more information about how things are set > > up: > > > > Output from gcc -v: > > Reading specs from > > c:/compilers/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-5/specs > > gcc version 2.95.3-5 (mingw special) > > > > I have msys 1.04 with echo and the recent added package > > > > I have msys installed at: c:/compilers/msys(/1.0/bin ...) > > I have mingw installed at: c:/compilers/mingw(/bin ...) > > > > I have in my system path (amongst many other items): > > c:\compilers\mingw\bin > > > > When I type ld at the dos shell I get: > > ld.exe: no input files > > > > When I type ld at the msys shell I get: > > c:\compilers\mingw\bin\ld.exe: no input files > > > > So MSYS finds ld.exe just fine. Why doesn't the configure script? > > > I've even tried copying the entire mingw folder to under the 1.0 > > directory in msys, removing any system path pointers to the original > > mingw directory, and just using the msys path pointer to gcc. I still > > get the full path prepended to ld, but no other programs. > > > > That's because the full path is given to ld in argv[0] and it's > programmed to use what ever argv[0] has for the name it prints. The > others obviously just care about the basename. > > > Does this help at all?? > > > > No, not really. What package are you building? Sorry if you've given > this before. > > Earnie. > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > |
From: Brian K. <bk...@on...> - 2002-02-23 02:32:03
|
I don't really know why ld is doing that, and I don't even know if that is the problem. I suppose the libsigc++ goes on the back burner for me. > -----Original Message----- > From: min...@li... [mailto:mingw-users- > ad...@li...] On Behalf Of Andres Rand > Sent: Friday, February 22, 2002 6:10 AM > To: Mingw Users List > Subject: Re: [Mingw-msys] Re: [Mingw-users] Question about aclocal > > > ----- Original Message ----- > From: "Brian Kropf" <bk...@on...> > To: "mingw msys" <min...@li...>; "mingw users" > <min...@li...> > Sent: Friday, February 22, 2002 3:34 AM > Subject: RE: [Mingw-msys] Re: [Mingw-users] Question about aclocal > > > > I've been trying to build libsigc++ > > > > This is the output I get from running configure > > > > $ ./configure > > loading cache ./config.cache > > checking for a BSD compatible install... /bin/install -c > > checking whether build environment is sane... yes > > checking whether make sets ${MAKE}... no > > checking for working aclocal... missing > > checking for working autoconf... missing > > checking for working automake... missing > > checking for working autoheader... missing > > checking for working makeinfo... found > > checking whether to enable maintainer-specific portions of Makefiles... > > no > > checking for gcc... gcc > > checking whether the C compiler (gcc ) works... yes > > checking whether the C compiler (gcc ) is a cross-compiler... no > > checking whether we are using GNU C... yes > > checking whether gcc accepts -g... yes > > checking how to run the C preprocessor... gcc -E > > checking host system type... i686-pc-mingw32 > > checking build system type... i686-pc-mingw32 > > checking for ranlib... ranlib > > checking for ld used by GCC... no > > configure: error: no acceptable ld found in $PATH > > > > The only thing I can think of for it not returning an "acceptable" ld is > > that the configure script is looking for ld.exe and not > > /c:/compilers/mingw/bin/ld.exe > > But why ld shows full path and not only ld.exe?? Other stuff do not show > full path. (I tryed it by hand). > > Andres. > > > > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users |
From: Earnie B. <ear...@ya...> - 2002-02-25 13:26:13
|
Brian Kropf wrote: > > I've been trying to build libsigc++ > Oh, yea, I did that one already. > This is the output I get from running configure > > $ ./configure > loading cache ./config.cache > checking for a BSD compatible install... /bin/install -c > checking whether build environment is sane... yes > checking whether make sets ${MAKE}... no > checking for working aclocal... missing > checking for working autoconf... missing > checking for working automake... missing > checking for working autoheader... missing > checking for working makeinfo... found > checking whether to enable maintainer-specific portions of Makefiles... > no > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes > checking whether the C compiler (gcc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether gcc accepts -g... yes > checking how to run the C preprocessor... gcc -E > checking host system type... i686-pc-mingw32 > checking build system type... i686-pc-mingw32 > checking for ranlib... ranlib > checking for ld used by GCC... no > configure: error: no acceptable ld found in $PATH > Take a look at the config.log file. What's it say about the error? Should be the last few lines of the file. > The only thing I can think of for it not returning an "acceptable" ld is > that the configure script is looking for ld.exe and not > /c:/compilers/mingw/bin/ld.exe > I doubt that that is the problem. The config.log should give a clue. The relative lines from my config.log file are: configure:1346: checking for ld used by GCC configure:1408: checking if the linker (/mingw/bin/ld) is GNU ld Looking at line 1346 of configure I find that it uses gcc -print-prog-name=ld to find the ld. Issuing that command I get c:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3-6/../../../../mingw32/bin/ld.exe Earnie. P.S.: There is no need to involve mingw-users in this discussion of MSYS. P.P.S.: What is the output of `set' from the MSYS command window? What is the output of `ls -l /c/compilers/mingw'? _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Brian K. <bk...@on...> - 2002-02-26 00:10:06
Attachments:
msys-set-output.txt
|
Oh the fun!!! > Take a look at the config.log file. What's it say about the error? > Should be the last few lines of the file. > Looking and the config.log wasn't very helpful for me. The last couple of lines are these: configure:1266: checking host system type configure:1287: checking build system type configure:1307: checking for ranlib configure:1346: checking for ld used by GCC > Looking at line 1346 of configure I find that it uses > gcc -print-prog-name=ld > to find the ld. Issuing that command I get > > c:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3- > 6/../../../../mingw32/bin/ld.exe > strange. Mine returns: $ gcc -print-prog-name=ld ld > P.S.: There is no need to involve mingw-users in this discussion of > MSYS. Ok, can do. > P.P.S.: What is the output of `set' from the MSYS command window? See attached output file > What is the output of `ls -l /c/compilers/mingw'? total 65 -rw-r--r-- 1 Brian Kr Administ 18347 Jul 22 2001 COPYING -rw-r--r-- 1 Brian Kr Administ 25765 Jul 22 2001 COPYING.LIB -rw-r--r-- 1 Brian Kr Administ 281 Jul 22 2001 README.LIBIBERTY drwxr-xr-x 4 Brian Kr Administ 0 Feb 19 11:18 SDL-1.2.3 drwxr-xr-x 2 Brian Kr Administ 0 Feb 19 11:24 bin drwxr-xr-x 3 Brian Kr Administ 0 Feb 21 18:03 doc drwxr-xr-x 7 Brian Kr Administ 0 Feb 21 18:03 include drwxr-xr-x 2 Brian Kr Administ 0 Dec 22 12:14 info-html drwxr-xr-x 4 Brian Kr Administ 0 Feb 21 18:03 lib drwxr-xr-x 3 Brian Kr Administ 0 Dec 22 12:14 man drwxr-xr-x 3 Brian Kr Administ 0 Feb 19 11:20 share -rw-r--r-- 1 Brian Kr Administ 11349 Feb 21 18:03 unins000.dat -rwxr-xr-x 1 Brian Kr Administ 72763 Feb 21 18:03 unins000.exe By the way, you built the full source package didn't you? That is the one I've been trying for. Brian Kropf > -----Original Message----- > From: Earnie Boyd [mailto:ear...@ya...] > Sent: Monday, February 25, 2002 8:27 AM > To: Brian Kropf > Cc: mingw msys > Subject: Re: [Mingw-msys] Re: [Mingw-users] Question about aclocal > > Brian Kropf wrote: > > > > I've been trying to build libsigc++ > > > > Oh, yea, I did that one already. > > > This is the output I get from running configure > > > > $ ./configure > > loading cache ./config.cache > > checking for a BSD compatible install... /bin/install -c > > checking whether build environment is sane... yes > > checking whether make sets ${MAKE}... no > > checking for working aclocal... missing > > checking for working autoconf... missing > > checking for working automake... missing > > checking for working autoheader... missing > > checking for working makeinfo... found > > checking whether to enable maintainer-specific portions of Makefiles... > > no > > checking for gcc... gcc > > checking whether the C compiler (gcc ) works... yes > > checking whether the C compiler (gcc ) is a cross-compiler... no > > checking whether we are using GNU C... yes > > checking whether gcc accepts -g... yes > > checking how to run the C preprocessor... gcc -E > > checking host system type... i686-pc-mingw32 > > checking build system type... i686-pc-mingw32 > > checking for ranlib... ranlib > > checking for ld used by GCC... no > > configure: error: no acceptable ld found in $PATH > > > > Take a look at the config.log file. What's it say about the error? > Should be the last few lines of the file. > > > The only thing I can think of for it not returning an "acceptable" ld is > > that the configure script is looking for ld.exe and not > > /c:/compilers/mingw/bin/ld.exe > > > > I doubt that that is the problem. The config.log should give a clue. > The relative lines from my config.log file are: > configure:1346: checking for ld used by GCC > configure:1408: checking if the linker (/mingw/bin/ld) is GNU ld > > Looking at line 1346 of configure I find that it uses > gcc -print-prog-name=ld > to find the ld. Issuing that command I get > > c:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3- > 6/../../../../mingw32/bin/ld.exe > > Earnie. > P.S.: There is no need to involve mingw-users in this discussion of > MSYS. > P.P.S.: What is the output of `set' from the MSYS command window? > What is the output of `ls -l /c/compilers/mingw'? > > > > > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > |
From: Earnie B. <ear...@ya...> - 2002-02-26 12:04:40
|
Brian Kropf wrote: > > Oh the fun!!! > > > Take a look at the config.log file. What's it say about the error? > > Should be the last few lines of the file. > > > Looking and the config.log wasn't very helpful for me. The last couple > of lines are these: > > configure:1266: checking host system type > configure:1287: checking build system type > configure:1307: checking for ranlib > configure:1346: checking for ld used by GCC > O.K. The needed information must have been in the unflushed buffer. :( > > Looking at line 1346 of configure I find that it uses > > gcc -print-prog-name=ld > > to find the ld. Issuing that command I get > > > > c:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3- > > 6/../../../../mingw32/bin/ld.exe > > > strange. Mine returns: > > $ gcc -print-prog-name=ld > ld > Not strange, see below. > > P.S.: There is no need to involve mingw-users in this discussion of > > MSYS. > > Ok, can do. > > > P.P.S.: What is the output of `set' from the MSYS command window? > > See attached output file > > > What is the output of `ls -l /c/compilers/mingw'? > > total 65 > -rw-r--r-- 1 Brian Kr Administ 18347 Jul 22 2001 COPYING > -rw-r--r-- 1 Brian Kr Administ 25765 Jul 22 2001 COPYING.LIB > -rw-r--r-- 1 Brian Kr Administ 281 Jul 22 2001 README.LIBIBERTY > drwxr-xr-x 4 Brian Kr Administ 0 Feb 19 11:18 SDL-1.2.3 > drwxr-xr-x 2 Brian Kr Administ 0 Feb 19 11:24 bin > drwxr-xr-x 3 Brian Kr Administ 0 Feb 21 18:03 doc > drwxr-xr-x 7 Brian Kr Administ 0 Feb 21 18:03 include > drwxr-xr-x 2 Brian Kr Administ 0 Dec 22 12:14 info-html > drwxr-xr-x 4 Brian Kr Administ 0 Feb 21 18:03 lib > drwxr-xr-x 3 Brian Kr Administ 0 Dec 22 12:14 man > drwxr-xr-x 3 Brian Kr Administ 0 Feb 19 11:20 share > -rw-r--r-- 1 Brian Kr Administ 11349 Feb 21 18:03 unins000.dat > -rwxr-xr-x 1 Brian Kr Administ 72763 Feb 21 18:03 unins000.exe > You're missing the mingw32 subdirectory. Where'd you put it? This is most likely your problem. I suggest that you extract the MinGW-1.1 file again to a depot directory and move the mingw32/ from it to your /c/comilers/mingw/ directory. Once you do that try the `gcc -print-file-name=ld' again to see if it finds it; it should put the full path. > By the way, you built the full source package didn't you? That is the > one I've been trying for. > Yes, I was able to build the full source package. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Brian K. <bk...@on...> - 2002-02-27 13:06:35
|
Yup you are an expert!! I removed the entire distribution and reinstalled it and now I can configure ;> Although this opens up a new can of worms :< Do you by chance have a cygpath defined? While making the libsig distro the libtool keeps printing: cygpath: command not found It's also dying on the .rc For some reason my windres will not compile resources directly .rc->.o So I found the proper makefile and included --use-temp-file, which got it going, but windres (and ms visual studio) can't seem to parse the VALUE definitions. Brian Kropf > -----Original Message----- > From: Earnie Boyd [mailto:ear...@ya...] > Sent: Tuesday, February 26, 2002 7:03 AM > To: Brian Kropf > Cc: mingw msys > Subject: Re: [Mingw-msys] Re: [Mingw-users] Question about aclocal > > Brian Kropf wrote: > > > > Oh the fun!!! > > > > > Take a look at the config.log file. What's it say about the error? > > > Should be the last few lines of the file. > > > > > Looking and the config.log wasn't very helpful for me. The last couple > > of lines are these: > > > > configure:1266: checking host system type > > configure:1287: checking build system type > > configure:1307: checking for ranlib > > configure:1346: checking for ld used by GCC > > > > O.K. The needed information must have been in the unflushed buffer. :( > > > > Looking at line 1346 of configure I find that it uses > > > gcc -print-prog-name=ld > > > to find the ld. Issuing that command I get > > > > > > c:/mingw/bin/../lib/gcc-lib/mingw32/2.95.3- > > > 6/../../../../mingw32/bin/ld.exe > > > > > strange. Mine returns: > > > > $ gcc -print-prog-name=ld > > ld > > > > Not strange, see below. > > > > P.S.: There is no need to involve mingw-users in this discussion of > > > MSYS. > > > > Ok, can do. > > > > > P.P.S.: What is the output of `set' from the MSYS command window? > > > > See attached output file > > > > > What is the output of `ls -l /c/compilers/mingw'? > > > > total 65 > > -rw-r--r-- 1 Brian Kr Administ 18347 Jul 22 2001 COPYING > > -rw-r--r-- 1 Brian Kr Administ 25765 Jul 22 2001 COPYING.LIB > > -rw-r--r-- 1 Brian Kr Administ 281 Jul 22 2001 README.LIBIBERTY > > drwxr-xr-x 4 Brian Kr Administ 0 Feb 19 11:18 SDL-1.2.3 > > drwxr-xr-x 2 Brian Kr Administ 0 Feb 19 11:24 bin > > drwxr-xr-x 3 Brian Kr Administ 0 Feb 21 18:03 doc > > drwxr-xr-x 7 Brian Kr Administ 0 Feb 21 18:03 include > > drwxr-xr-x 2 Brian Kr Administ 0 Dec 22 12:14 info-html > > drwxr-xr-x 4 Brian Kr Administ 0 Feb 21 18:03 lib > > drwxr-xr-x 3 Brian Kr Administ 0 Dec 22 12:14 man > > drwxr-xr-x 3 Brian Kr Administ 0 Feb 19 11:20 share > > -rw-r--r-- 1 Brian Kr Administ 11349 Feb 21 18:03 unins000.dat > > -rwxr-xr-x 1 Brian Kr Administ 72763 Feb 21 18:03 unins000.exe > > > > You're missing the mingw32 subdirectory. Where'd you put it? This is > most likely your problem. I suggest that you extract the MinGW-1.1 file > again to a depot directory and move the mingw32/ from it to your > /c/comilers/mingw/ directory. Once you do that try the `gcc > -print-file-name=ld' again to see if it finds it; it should put the full > path. > > > By the way, you built the full source package didn't you? That is the > > one I've been trying for. > > > > Yes, I was able to build the full source package. > > Earnie. > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > |
From: Earnie B. <ear...@ya...> - 2002-02-27 13:54:40
|
Brian Kropf wrote: > > Yup you are an expert!! > I removed the entire distribution and reinstalled it and now I can > configure ;> Although this opens up a new can of worms :< Do you by > chance have a cygpath defined? While making the libsig distro the > libtool keeps printing: cygpath: command not found > Update to MSYS-1.0.5 and rerun configure. To answer your question directly, no I don't have a cygpath defined, however, it used to be a problem. I think it had to do with a missing echo.exe but it's been a while and a lot of water has gone under the bridge since then. > It's also dying on the .rc For some reason my windres will not compile > resources directly .rc->.o So I found the proper makefile and included > --use-temp-file, which got it going, but windres (and ms visual studio) > can't seem to parse the VALUE definitions. > Don't have an answer for this. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Earnie B. <ear...@ya...> - 2002-02-20 14:08:21
|
Brian Kropf wrote: > > Here is a different, but related question... > > I took cygwin out of my Path variable (winXP) I don't think I'll need it > anymore anyway. But now when I try to configure, it gets to the point > where it looks for gcc's ld and can't find it. It finds the other > pieces before that so I wonder what gives?? It says it can't find ld on > the path. Is there a path to set in msys that is separate from the > external path?? > My PATH is set to: /bin:/mingw/bin:/c/IT_Comm/Oracle/Net/bin:/c/WINNT/system32:/c/WINNT:/c/WINNT/System32/WBEM I have MinGW-1.1 installed in C:\mingw and my /etc/fstab file contains: $ cat /etc/fstab c:/mingw /mingw > BTW thanks for your prompt responses!!! > Wednesday is my play day. ;) I hope to have MSYS-1.0.5 uploaded by the end of my day. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |