|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
|
|
make: *** [debug_base_make] Error 255Hi, When I try to compile around 300 *.c files with (OS: windows
xp professional ) gnu make 3.80 am getting an error like The input line is too long. make: *** [debug_base_make] Error 255 Hope it is not limitation with xp. Can you please let me know what kind
of error is this. I got similar kind of error earlier but it was resolved by
reducing the length of the folder names. Now my folder structure have almost
single character as names !! Still am getting the error. Please sagest me some solution and also help full if you can tell why
is this error. Thanks in advance.. Thanks & Regards, Nandish S Matad nandishs@... & nandishmatad@... _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
|
|
RE: make: *** [debug_base_make] Error 255It is indeed a limitation with XP, the
cmd your makefile is trying to invoke is exceeding the character length limits
of Windows’ cmd processor. You’ll need to find a way to divide
the command up into smaller pieces. It is a little difficult to provide a
specific solution without seeing what your make rule is doing. Hope this helps, - From:
help-make-bounces+raleigh.rinehart=ti.com@...
[mailto:help-make-bounces+raleigh.rinehart=ti.com@...] On Behalf Of Nandish S. Matad Hi, When I try to compile around 300 *.c files with (OS: windows
xp professional ) gnu make 3.80 am getting an error like The input line is too long. make: *** [debug_base_make] Error 255 Hope it is not limitation with xp. Can you please let me know what kind
of error is this. I got similar kind of error earlier but it was resolved by
reducing the length of the folder names. Now my folder structure have almost
single character as names !! Still am getting the error. Please sagest me some solution and also help full if you can tell why
is this error. Thanks in advance.. Thanks & Regards, Nandish S Matad nandishs@... & nandishmatad@... _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
|
|
RE: make: *** [debug_base_make] Error 255You are correct Raleigh, thanks for pointing out the exact problem. As a solution we have used cygwin. cygwin does not have any limit on the cmd line length as it uses standard UNIX/Linux development environment on Windows including APIs and command shells.
Thanks & regards, Nandish S Matad
|
|
|
if SHELL not set, COMSPEC used - not working?The GNU Make manual says:
"On MS-DOS, if SHELL is not set, the value of the variable COMSPEC (which is always set) is used instead." This does not seem to work for me? Why, is this a bug? Let me show you - as you can see, make did not call upon the value in COMSPEC, but instead went to a Unix shell, which I also have installed, and which does not have "ver" command: D:\tmp>ver Microsoft Windows XP [Version 5.1.2600] D:\tmp>type makefile foobar: ver D:\tmp>set COMSPEC ComSpec=C:\WINDOWS\system32\cmd.exe D:\tmp>make foobar ver process_begin: CreateProcess(NULL, ver, ...) failed. make (e=2): The system cannot find the file specified. make: *** [foobar] Error 2 D:\tmp> _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
|
|
Re: if SHELL not set, COMSPEC used - not working?[Please break long lines at, say, 72 characters--that would make it
much easier to reply. Thanks.] On 2009-11-05 00:51Z, Mark Galeck (CW) wrote: > The GNU Make manual says: > > "On MS-DOS, if SHELL is not set, the value of the variable COMSPEC > (which is always set) is used instead." > > This does not seem to work for me? Why, is this a bug? For me, it seems to work as you expect, using a native msw build of the original make-3.81 sources: C:\cygwin\home\chicares\tmp>\usr\bin\make -f foobar ver Microsoft Windows XP [Version 5.1.2600] > Let me show you - as you can see, make did not call upon the value in > COMSPEC, but instead went to a Unix shell, which I also have installed, Could it be that you also have a *nix 'make' installed, which might be called instead of a native 'make'? If you would add these lines: echo $(MAKE) echo $(SHELL) to your default rule, then we'd know for sure. _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
|
|
Re: if SHELL not set, COMSPEC used - not working?> From: "Mark Galeck (CW)" <mgaleck@...>
> Date: Wed, 4 Nov 2009 16:51:15 -0800 > Accept-Language: en-US > acceptlanguage: en-US > Cc: > > The GNU Make manual says: > > "On MS-DOS, if SHELL is not set, the value of the variable COMSPEC (which is always set) is used instead." > > This does not seem to work for me? Why, is this a bug? No, it's because the above says "On MS-DOS", while you are on Windows: > D:\tmp>ver > > Microsoft Windows XP [Version 5.1.2600] On MS-Windows, you need to explicitly say "SHELL=cmd.exe" in the Makefile (or on the Make command line) to get this behavior. _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
|
|
Re: if SHELL not set, COMSPEC used - not working?> Date: Thu, 05 Nov 2009 02:09:32 +0000
> From: Greg Chicares <gchicares@...> > Cc: > > For me, it seems to work as you expect, using a native msw build > of the original make-3.81 sources: > > C:\cygwin\home\chicares\tmp>\usr\bin\make -f foobar > ver > > Microsoft Windows XP [Version 5.1.2600] Probably because you don't have a sh.exe anywhere on your native Windows PATH. The Windows port of Make always invokes a Unixy shell if it can find it, but falls back on cmd.exe. This is regardless of whether SHELL is or isn't set in the environment. _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
|
|
RE: if SHELL not set, COMSPEC used - not working?>Could it be that you also have a *nix 'make' installed, which might
be called instead of a native 'make'? If you would add these lines: echo $(MAKE) echo $(SHELL) to your default rule, then we'd know for sure. I think I am calling the correct make, as you can see, it was built for i386-pc, "mingw32" is some kind of GNU distribution, not sure exactly: D:\tmp>type makefile foobar: @echo $(MAKE) @echo $(SHELL) ver D:\tmp>make foobar make C:/Tools/cygwin/bin/sh.exe ver process_begin: CreateProcess(NULL, ver, ...) failed. make (e=2): The system cannot find the file specified. make: *** [foobar] Error 2 D:\tmp>make -version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-pc-mingw32 D:\tmp> _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
|
|
RE: if SHELL not set, COMSPEC used - not working?>No, it's because the above says "On MS-DOS", while you are on Windows:
Hmm, thank you! I thought that "MS-DOS" always means "or Windows". OK, thank you for correcting me. _______________________________________________ Help-make mailing list Help-make@... http://lists.gnu.org/mailman/listinfo/help-make |
| Free embeddable forum powered by Nabble | Forum Help |