Re: Make error messages

[Paul Smith]

On Wed, 2019-09-11 at 08:44 +0200, Andreas Schwab wrote:
> On Sep 10 2019, Paul Smith  wrote:
> 
> > That didn't work, however, because particularly in recursive make
> > the makefile name is likely not qualified with a path, but the
> > current working directory when the build is invoked is not the same
> > as the one where make is invoked--thus "Makefile" is at best
> > ambiguous.
> 
> But isn't that the same situation as with any other error message in
> a recursive make, which Emacs already handles correctly (with the
> help of make --print-directory)?

Thanks for getting me to look into this more deeply.

The problem is not print-directory, etc.  The problem is that Emacs
compile mode doesn't have a matcher for error messages generated by GNU
make when a target fails.  As such it matches some other regex in
compilation-error-regexp-alist-alist and computes the filename
incorrectly.

I've sent a patch to Emacs for compile.el which adds a matching regex
for GNU make error messages, and assigns them the INFO level since they
are usually not needed, but sometimes is is very handy to be able to
jump to the makefile recipe.

In the meantime I've added this to my init.el:

;; Add support for GNU make error matching, if it doesn't yet exist
(with-eval-after-load 'compile
  (or (member 'gmake compilation-error-regexp-alist)
  (progn
(setf (alist-get 'gmake compilation-error-regexp-alist-alist)
  '(": \\*\\*\\* \\[\\(\\(.+?\\):\\([0-9]+\\): .+\\)\\]"
2 3 nil 0 1))
(add-to-list 'compilation-error-regexp-alist 'gmake

I'm going to revert the change I made to GNU make to use ";" instead of
":" between the filename and line number (that was never part of any
release of GNU make) and go back to ":".


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Re: Make error messages

[Andreas Schwab]

On Sep 10 2019, Paul Smith  wrote:

> That didn't work, however, because particularly in recursive make the
> makefile name is likely not qualified with a path, but the current
> working directory when the build is invoked is not the same as the one
> where make is invoked--thus "Makefile" is at best ambiguous.

But isn't that the same situation as with any other error message in a
recursive make, which Emacs already handles correctly (with the help of
make --print-directory)?

Andreas.

-- 
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Make error messages

[Paul Smith]

I've gone through a few iterations of the format of make error messages
and I'm still not happy.

Originally we didn't put the makefile name/linenumber in the error at
all when a recipe failed (we did for syntax errors in makefiles of
course).  Then someone asked for make to show a reference to the recipe
that failed when make detected an error, so I changed it to this:

  make: *** [Makefile:3: myprog.o] Error 1

The idea was to use the same format that the compiler, etc. used so
that (for example) Emacs compile mode would be able to jump to errors.

That didn't work, however, because particularly in recursive make the
makefile name is likely not qualified with a path, but the current
working directory when the build is invoked is not the same as the one
where make is invoked--thus "Makefile" is at best ambiguous.

So now I've changed the output to use a semicolon between the name and
the line number to try to "hide" this from Emacs compile mode:

  make: *** [Makefile;3: myprog.o] Error 1
 ^
This fixed the problem at least for Emacs compile mode; it no longer
recognizes this as an error line.  But it still seems suboptimal to me.

I've been wondering if we shouldn't make an attempt to show the
"correct" path to the makefile in these error messages.  The way I was
imagining it could work is something like this:

(a) when make is invoked it looks for special environment variable,
like MAKE_ROOTDIR or something.  If that value is set it is remembered.
If that variable is not set then it is set to the value of
current_directory (already computed in main() using getcwd()) and
exported.  The result is that MAKE_ROOTDIR should be the current
working directory of the user when they invoked the top-level make,
even if we're in a recursive make.

(b) when make wants to generate an error message containing the name of
the current makefile, it computes the fully-qualified path of the
makefile then strips off the prefix MAKE_ROOTDIR and prints that as the
name of the makefile.  Of course if the path doesn't start with
MAKE_ROOTDIR we print the fully-qualified path.

Obviously there are some weirdnesses here... for example the ever-
present issue of symlinks yielding multiple different paths to the same
directory, but in that situation you'd simply get the fully-qualified
makefile path.

Also, if you had a script that changed directory then invoked the root
make it would not work... but your script could pre-set $MAKE_ROOTDIR
before starting make.

Or we could always print the fully-qualified path but that may look
gross.

This would also allow us to go back to the error message with a ":"
since Emacs could jump to the correct place in the correct makefile.

I dunno.  Thoughts?


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

about EOS make error

[thutt]

ying ye writes:
 > Hi 
 >   
 > The following error occurred when I executed "./eosio_build.sh".
 > 

 There is no actionable information in your message.  You have not
 stated what the problem is, or what you are trying to accomplish, or
 how this is an issue with Gnu Make (this mailing list is for
 discussing Gnu Make).



 > 该程序为 x86_64-pc-linux-gnu 编译
 > 报告错误到 
 > Error compiling MongoDB C driver.
 > 
 > Exiting now.
 > 

 It looks more like an issue in building MongoDB.  I think you will
 find more help in MongoDB mailing lists.

-- 
Does a photon exist before someone sees it?


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Re: make error

[Tim Murphy]

@psmith - happens to me all the time even on good weeks. :-)


Carolina,

In the makefile this line is wrong:

F90  = /opt/intel/composer_xe_2011_sp1.6.233

It tries to set the variable F90 to the path of the Intel Fortran 90
compiler but somehow this is a directory on your computer rather than
a program.

Later on the makefile tries to use this variable to execute the compiler:

mocassin:
$(F90) $(OPT1) -o mocassin $(source1) $(LIBS)


From a quick look at the intel website, I get the impression that the
compiler's name is ifort.  That means that the F90 variable should
probably have ifort on the end - as examples:
/opt/intel/composer_xe_2011_sp1.6.233/bin/ifort
or maybe
/opt/intel/composer_xe_2011_sp1.6.233/ifort

you could try finding it like this:
find /opt/intel/composer_xe_2011_sp1.6.233 -type f -iname 'ifort'


Regards,

Tim
On 5 October 2011 16:16, Paul Smith psm...@gnu.org wrote:
 On Wed, 2011-10-05 at 16:07 +0100, Tim Murphy wrote:
 Your makefile is trying to execure a directory rather than a program.

 Hah!  I didn't even notice it was a directory.  Good catch.

 I'm having a really bad week.





-- 
You could help some brave and decent people to have access to
uncensored news by making a donation at:

http://www.thezimbabwean.co.uk/friends/

___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Re: make error

[Carolina Carneiro]

Thanks everybody for help!!
I'm starting to use linux and I'm really lost!

Tim, you were right!! Thank you very much!!

Carolina.

2011/10/6 Tim Murphy tnmur...@gmail.com

 @psmith - happens to me all the time even on good weeks. :-)


 Carolina,

 In the makefile this line is wrong:

 F90  = /opt/intel/composer_xe_2011_sp1.6.233

 It tries to set the variable F90 to the path of the Intel Fortran 90
 compiler but somehow this is a directory on your computer rather than
 a program.

 Later on the makefile tries to use this variable to execute the compiler:

 mocassin:
$(F90) $(OPT1) -o mocassin $(source1) $(LIBS)


 From a quick look at the intel website, I get the impression that the
 compiler's name is ifort.  That means that the F90 variable should
 probably have ifort on the end - as examples:
 /opt/intel/composer_xe_2011_sp1.6.233/bin/ifort
 or maybe
 /opt/intel/composer_xe_2011_sp1.6.233/ifort

 you could try finding it like this:
 find /opt/intel/composer_xe_2011_sp1.6.233 -type f -iname 'ifort'


 Regards,

 Tim
 On 5 October 2011 16:16, Paul Smith psm...@gnu.org wrote:
  On Wed, 2011-10-05 at 16:07 +0100, Tim Murphy wrote:
  Your makefile is trying to execure a directory rather than a program.
 
  Hah!  I didn't even notice it was a directory.  Good catch.
 
  I'm having a really bad week.
 
 



 --
 You could help some brave and decent people to have access to
 uncensored news by making a donation at:

 http://www.thezimbabwean.co.uk/friends/

___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

make error

[Carolina Carneiro]

Hi,

I'm trying to use make to compile the drivers of a program I have to use,
called MOCASSIN.
But when I type make mocassin, this error menssage appears:

root@carol-HP-Pavilion-dv5-Notebook-PC:/home/carol/mocassin/mocassin.2.02.69#
make mocassin
/opt/intel/composer_xe_2011_sp1.6.233 0.5 -o mocassin source/infnan.f90
source/constants_mod.f90 source/vector_mod.f90 source/common_mod.f90
source/interpolation_mod.f90 source/set_input_mod.f90 source/hydro_mod.f90
source/ph_mod.f90 source/composition_mod.f90 source/continuum_mod.f90
source/ionization_mod.f90 source/pathIntegration_mod.f90 source/grid_mod.f90
source/dust_mod.f90 source/emission_mod.f90 source/photon_mod.f90
source/update_mod.f90 source/output_mod.f90 source/iteration_mod.f90
source/mocassin.f90  /home/carol/mocassin/mpich2-install
make: execvp: /opt/intel/composer_xe_2011_sp1.6.233: Permission denied
make: *** [mocassin] Error 127

I don't know what's wrong, since I'm root and all permissions are openned:

4 drwxrwxrwx 5 root root4096 2011-09-22 23:39 composer_xe_2011_sp1.6.233

I'm sending the makefile.

Can you help me?

Thank you for your atention,
Carolina.


makefile
Description: Binary data
___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

Re: make error

[Tim Murphy]

Your makefile is trying to execure a directory rather than a program.

Cheers,

Tim

On 5 October 2011 15:48, Carolina Carneiro caro...@astro.ufrj.br wrote:
 Hi,

 I'm trying to use make to compile the drivers of a program I have to use,
 called MOCASSIN.
 But when I type make mocassin, this error menssage appears:

 root@carol-HP-Pavilion-dv5-Notebook-PC:/home/carol/mocassin/mocassin.2.02.69#
 make mocassin
 /opt/intel/composer_xe_2011_sp1.6.233 0.5 -o mocassin source/infnan.f90
 source/constants_mod.f90 source/vector_mod.f90 source/common_mod.f90
 source/interpolation_mod.f90 source/set_input_mod.f90 source/hydro_mod.f90
 source/ph_mod.f90 source/composition_mod.f90 source/continuum_mod.f90
 source/ionization_mod.f90 source/pathIntegration_mod.f90 source/grid_mod.f90
 source/dust_mod.f90 source/emission_mod.f90 source/photon_mod.f90
 source/update_mod.f90 source/output_mod.f90 source/iteration_mod.f90
 source/mocassin.f90  /home/carol/mocassin/mpich2-install
 make: execvp: /opt/intel/composer_xe_2011_sp1.6.233: Permission denied
 make: *** [mocassin] Error 127

 I don't know what's wrong, since I'm root and all permissions are openned:

 4 drwxrwxrwx 5 root root    4096 2011-09-22 23:39 composer_xe_2011_sp1.6.233

 I'm sending the makefile.

 Can you help me?

 Thank you for your atention,
 Carolina.

 ___
 Bug-make mailing list
 Bug-make@gnu.org
 https://lists.gnu.org/mailman/listinfo/bug-make





-- 
You could help some brave and decent people to have access to
uncensored news by making a donation at:

http://www.thezimbabwean.co.uk/friends/

___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make

/bootstrap-prefix.sh $EPREFIX/tmp make Error

[W Stewart Gilman Jr.]

* Bootstrapping Gentoo prefixed portage installation using
* host:   i386-apple-darwin10
* prefix: /Users/reciprocity/Gentoo/tmp
* ready to bootstrap make
* Bootstrapping make
* Fetching make-3.81.tar.gz
Trying 137.226.34.42...
Requesting http://distfiles.gentoo.org/distfiles/make-3.81.tar.gz
100% 
|***|
  1527 KiB  367.01 KiB/s00:00 ETA
1564560 bytes retrieved in 00:04 (366.95 KiB/s)
* Unpacking make
* Compiling make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... grep: temp=: No such file or directory
no
checking for i386-apple-darwin10-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... grep: ^ *+: No such file or 
directory
yes
checking whether gcc accepts -g... grep: ^ *+: No such file or directory
yes
checking for gcc option to accept ANSI C... grep: ^ *+: No such file or 
directory
none needed
grep: ^ *+: No such file or directory
checking for style of include used by make... grep: ing directory: No such file 
or directory
none
checking dependency style of gcc... none
checking for a BSD-compatible install... /usr/bin/install -c
checking for i386-apple-darwin10-ranlib... no
checking for ranlib... ranlib
checking how to run the C preprocessor... grep: ^ *+: No such file or directory
grep: ^ *+: No such file or directory
gcc -E
grep: ^ *+: No such file or directory
grep: ^ *+: No such file or directory
checking for ar... ar
checking for perl... perl
checking build system type... i386-apple-darwin10
checking host system type... i386-apple-darwin10
checking for egrep... egrep
checking for AIX... no
checking for library containing strerror... grep: ^ *+: No such file or 
directory
none required
checking for ANSI C header files... grep: ^ *+: No such file or directory
rm: conftest.dSYM: is a directory
no
checking for sys/types.h... grep: ^ *+: No such file or directory
yes
checking for sys/stat.h... grep: ^ *+: No such file or directory
yes
checking for stdlib.h... grep: ^ *+: No such file or directory
yes
checking for string.h... grep: ^ *+: No such file or directory
yes
checking for memory.h... grep: ^ *+: No such file or directory
yes
checking for strings.h... grep: ^ *+: No such file or directory
yes
checking for inttypes.h... grep: ^ *+: No such file or directory
yes
checking for stdint.h... grep: ^ *+: No such file or directory
yes
checking for unistd.h... grep: ^ *+: No such file or directory
yes
checking minix/config.h usability... grep: ^ *+: No such file or directory
no
checking minix/config.h presence... grep: ^ *+: No such file or directory
no
checking for minix/config.h... no
checking for function prototypes... yes
checking for string.h... (cached) yes
checking whether NLS is requested... no
checking for msgfmt... no
checking for gmsgfmt... :
checking for xgettext... no
checking for msgmerge... no
checking for ld used by GCC... /usr/libexec/gcc/i686-apple-darwin10/4.2.1/ld
checking if the linker (/usr/libexec/gcc/i686-apple-darwin10/4.2.1/ld) is GNU 
ld... no
checking for shared library run path origin... grep: Apple: No such file or 
directory
done
checking whether NLS is requested... no
checking whether to use NLS... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... grep: ^ *+: No 
such file or directory
no
rm: conftest.dSYM: is a directory
checking for _LARGE_FILES value needed for large files... grep: ^ *+: No such 
file or directory
no
rm: conftest.dSYM: is a directory
checking for library containing getpwnam... grep: ^ *+: No such file or 
directory
none required
checking for ANSI C header files... (cached) no
checking for dirent.h that defines DIR... grep: ^ *+: No such file or directory
yes
checking for library containing opendir... grep: ^ *+: No such file or directory
none required
checking whether stat file-mode macros are broken... rm: conftest.dSYM: is a 
directory
no
checking whether time.h and sys/time.h may both be included... grep: ^ *+: No 
such file or directory
yes
checking for stdlib.h... (cached) yes
checking locale.h usability... grep: ^ *+: No such file or directory
yes
checking locale.h presence... grep: ^ *+: No such file or directory
yes
checking for locale.h... yes
checking for unistd.h... (cached) yes
checking limits.h usability... grep: ^ *+: No such file or directory
yes
checking limits.h presence... grep: ^ *+: No such file or directory
yes
checking for limits.h... yes
checking fcntl.h usability... grep: ^ *+: No such file or directory

Re: Make Error - trouble shooting

[Paul Smith]

On Wed, 2011-02-23 at 14:58 +0900, JamesHur(허성삼) wrote:

 This is James Hur from Korea, I’ve been tried to solve specific
 problem as follow and I got the answer through the googling.
 
 -   Problem : When I run make with Makefile, I got error message
 as : Makefile:1458:mixed implicit and normal rules. Stop
 
 -   And I found the answer by this web-page :
 http://www.linuxquestions.org/questions/linux-software-2/error-mixed-implicit-and-normal-rules-while-trying-to-build-busybox-826795/
 
 -   He had same problem and fixed it up. 
 
 -   However I got trouble still due to don’t know how to change
 the code.
 
 -   Maybe I get the source code of make utility from gnu.org and
 should try to change the source code, could you let me know the way
 how to fix it up? Pls.

I seriously doubt that you want to change the code for GNU make, but if
you do you can find it at ftp://ftp.gnu.org/pub/gnu/make/

You can also download the previous version (3.81) which still contains
the bug in it that the makefiles you're using are exploiting.  The
reason the newer version of Linux works and the older does not is that
the makefiles were fixed in the newer ones.

Or you can fix the makefiles.

-- 
---
 Paul D. Smith psm...@gnu.org  Find some GNU make tips at:
 http://www.gnu.org  http://make.mad-scientist.net
 Please remain calm...I may be mad, but I am a professional. --Mad Scientist


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Make Error - trouble shooting

[허성삼]

Hello, GNU-Make

 

This is James Hur from Korea, I’ve been tried to solve specific problem as
follow and I got the answer through the googling.

-   Problem : When I run make with Makefile, I got error message as :
Makefile:1458:mixed implicit and normal rules. Stop

-   And I found the answer by this web-page : http://www.linuxquestions.
org/questions/linux-software-2/error-mixed-implicit-and-normal-rules-while-
trying-to-build-busybox-826795/

-   He had same problem and fixed it up. 

-   However I got trouble still due to don’t know how to change the
code.

-   Maybe I get the source code of make utility from gnu.org and should
try to change the source code, could you let me know the way how to fix it
up? Pls.

 

For your reference, below are my developing environment :

-   System : Notebook, Centrino Duo core and 200G HDD, 1G RAM

-   OS : Linux Fedora 14, (2.6.35.6-45.fc14.i686.PAE)

-   Make version : 3.82

In addition, I had no error under above kernel version, but only occur the
error with kernel version : 2.6.21

 

Thanks in advanced

James Hur

==

James Hur 허 성 삼(許盛森)

(주)옴니시스템 기술연구소 책임연구원

OMNI System RD Center

Senior Research Engineer

Tel : 070-4169-8683(Direct)

C.P : 010-8909-3279

(+82-10-8909-3279)

Fax : 02-461-8752

Email : h...@omnisystem.co.kr

www.omnisystem.co.kr

==

 

___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Make error

[Tejbahadur Singh // Viva]

hi
   while make command i got following error please reply soon

make  all-recursive
make[1]: Entering directory `/root/mailmonitor/pango-1.21.1'
Making all in pango
make[2]: Entering directory `/root/mailmonitor/pango-1.21.1/pango'
( cd .  glib-mkenums \
--fhead #ifndef __PANGO_ENUM_TYPES_H__\n#define
__PANGO_ENUM_TYPES_H__\n\n#include glib-object.h\n\nG_BEGIN_DECLS\n \
--fprod /* enumerations from \@filen...@\ */\n \
--vhead GType @enum_n...@_get_type (void);\n#define
pango_ty...@enumshort@ (@enum_n...@_get_type())\n \
--ftail G_END_DECLS\n\n#endif /*
__PANGO_ENUM_TYPES_H__ */ \
pango.h pango-attributes.h pango-bidi-type.h pango-break.h
pango-context.h pango-coverage.h pango-engine.h pango-font.h pango-fontmap.h
pango-fontset.h pango-glyph.h pango-glyph-item.h pango-gravity.h
pango-item.h pango-language.h pango-layout.h pango-matrix.h pango-modules.h
pango-renderer.h pango-script.h pango-tabs.h pango-types.h pango-utils.h ) 
tmp-pango-enum-types.h \
 (cmp -s tmp-pango-enum-types.h pango-enum-types.h || cp
tmp-pango-enum-types.h pango-enum-types.h ) \
 rm -f tmp-pango-enum-types.h \
 echo timestamp  s-enum-types-h
/bin/sh: line 1: glib-mkenums: command not found
make[2]: *** [s-enum-types-h] Error 127
make[2]: Leaving directory `/root/mailmonitor/pango-1.21.1/pango'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/mailmonitor/pango-1.21.1'
make: *** [all] Error 2
___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: Make error

[Paul Smith]

On Wed, 2010-09-01 at 14:15 +0530, Tejbahadur Singh // Viva wrote:
 /bin/sh: line 1: glib-mkenums: command not found
 make[2]: *** [s-enum-types-h] Error 127

This mailing list is for problems with the GNU make program itself.  We
can't possibly help troubleshoot all the hundreds of thousands of
software packages that use make to control their builds.

The above issue is caused by the software you're trying to build
failing, not GNU make failing.  You'll have to find a mailing list
dedicated to supporting that software (looks like pango-1.21.1) and ask
them why your build is failing.

If I had to guess I'd say you need to install a package on your system
(whatever it is) that provides the glib-mkenums command, because it's
missing.

That's about all I can say.


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

partd make error

[zhaomingyang]

Report bugs to bug-make@gnu.org

# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking whether gcc needs -traditional... no
checking whether gcc and cc understand -c and -o together... yes
checking for ranlib... ranlib
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) 
-std=gnu99
checking for a usable (O_DIRECT-supporting) temporary dir... .
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for working alloca.h... yes
checking for alloca... yes
checking whether wchar.h uses 'inline' correctly... yes
checking for btowc... yes
checking for canonicalize_file_name... yes
checking for getcwd... yes
checking for readlink... yes
checking for realpath... yes
checking for __fpending... yes
checking for fsync... yes
checking for gettimeofday... yes
checking for lstat... yes
checking for mbsinit... yes
checking for mbrtowc... yes
checking for mprotect... yes
checking for nl_langinfo... yes
checking for pathconf... yes
checking for isblank... yes
checking for iswctype... yes
checking for wcscoll... yes
checking for strndup... yes
checking for wcrtomb... yes
checking for iswcntrl... yes
checking for dup2... yes
checking for setenv... yes
checking for symlink... yes
checking for wctob... yes
checking for nl_langinfo and CODESET... yes
checking for a traditional french locale... none
checking for size_t... yes
checking whether malloc, realloc, calloc are POSIX compliant... yes
checking whether // is distinct from /... no
checking whether realpath works... yes
checking for sys/param.h... yes
checking for errno.h... yes
checking for stdio_ext.h... yes
checking for getopt.h... yes
checking for sys/time.h... yes
checking for stdint.h... (cached) yes
checking for wchar.h... yes
checking for inttypes.h... (cached) yes
checking for langinfo.h... yes
checking for sys/mman.h... yes
checking for locale.h... yes
checking for stdarg.h... yes
checking for stddef.h... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for sys/socket.h... yes
checking for string.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for time.h... yes
checking for unistd.h... (cached) yes
checking for wctype.h... yes
checking for fcntl.h... yes
checking for priv.h... no
checking for blkid/blkid.h... no
checking whether system is Windows or MSDOS... no
checking whether the preprocessor supports include_next... yes
checking for complete errno.h... yes
checking whether strerror_r is declared... yes
checking for strerror_r... yes
checking whether strerror_r returns char *... yes
checking for inline... inline
checking for getopt.h... (cached) yes
checking for getopt_long_only... yes
checking whether optreset is declared... no
checking whether getopt is POSIX compatible... yes
checking for working GNU getopt function... yes
checking whether getenv is declared... yes
checking for C/C++ restrict keyword... __restrict
checking for struct timeval... yes
checking whether gettimeofday is declared without a macro... yes
checking for long long int... yes
checking for unsigned long long int... yes
checking whether stdint.h conforms to C99... yes

Re: partd make error

[Paul Smith]

On Tue, 2010-05-25 at 11:14 -0400, zhaomingyang wrote:
 Report bugs to bug-make@gnu.org

Report bugs in _GNU make_ to this mailing list.

We don't support every project that uses make as a build tool: if you
have a problem with a given project's build then you have to contact the
developers of that project (in this case, partd): they'll have their own
mailing list, bug trackers, etc.

Check the source code directory for information in files such as BUGS,
README, INSTALL, etc.

-- 
---
 Paul D. Smith psm...@gnu.org  Find some GNU make tips at:
 http://www.gnu.org  http://make.mad-scientist.net
 Please remain calm...I may be mad, but I am a professional. --Mad Scientist


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: make error but no message

[Jeremiah Perry]

Okay, I just ran make 3.81 on Ubuntu 8.10 and had the same problem. I
put those three files in a directory, type make, and nothing
happens--nothing is built, and no error messages. It's not a big deal
but it does seem like a bug. Anyone know what might be happening?

Jeremiah

On Thu, Mar 12, 2009 at 3:17 PM, Jeremiah Perry
jeremiah.pe...@gmail.com wrote:
 I'm using 3.81 on cygwin. I found the problem on a prebuilt binary,
 then I compiled make from source today (on cygwin) to see if the
 problem would go away but it didn't. I suppose it could be a cygwin
 problemI'll try running it on Linux when I get home tonight.

 Jeremiah

 On Thu, Mar 12, 2009 at 3:02 PM, Sam Ravnborg s...@ravnborg.org wrote:
 On Thu, Mar 12, 2009 at 02:07:56PM -0700, Jeremiah Perry wrote:
 Hi,

 I don't know if the following is a bug or not, but it came to my
 attention recently. I ran make on a project only to have make stop
 abruptly with no error messages. After some digging, I found one of my
 dependencies referred to a non-existent file. My dependency rules are
 in .d files that I then -include into the makefile. See the code
 example below. It seems this -include throws make off somehow so it
 doesn't issue any error messages. However, when I put the dependencies
 explicitly into the makefile, make tells me *** No rule to make
 target `doesnt_exist.h', needed by `test.o'. Stop., so that seems to
 be fine.

 I tried it here.
 With make 3.80 it works as expected. I do not have 3.81 handy right now.
 Which version of make did you use?

        Sam




___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

make error but no message

[Jeremiah Perry]

Hi,

I don't know if the following is a bug or not, but it came to my
attention recently. I ran make on a project only to have make stop
abruptly with no error messages. After some digging, I found one of my
dependencies referred to a non-existent file. My dependency rules are
in .d files that I then -include into the makefile. See the code
example below. It seems this -include throws make off somehow so it
doesn't issue any error messages. However, when I put the dependencies
explicitly into the makefile, make tells me *** No rule to make
target `doesnt_exist.h', needed by `test.o'. Stop., so that seems to
be fine.

Thanks,

Jeremiah

--
Makefile:
SRC = $(wildcard *.c)
OBJ = $(SRC:.c=.o)

CC = gcc

all: test

.PHONY = test
test: $(OBJ)
$(CC) -o test $(OBJ)

%.d : %.c
@echo Making $@ from $
@bash -ec '$(CC) -MM $ | sed s/$*.o/ $@/g  $@'

-include $(SRC:.c=.d)

--
test.c:
#include stdio.h

int main(int argc, char** argv)
{
  puts(just a test\n);
}

--
test.d:
test.o test.d: test.c doesnt_exist.h
--


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: make error but no message

[Sam Ravnborg]

On Thu, Mar 12, 2009 at 02:07:56PM -0700, Jeremiah Perry wrote:
 Hi,
 
 I don't know if the following is a bug or not, but it came to my
 attention recently. I ran make on a project only to have make stop
 abruptly with no error messages. After some digging, I found one of my
 dependencies referred to a non-existent file. My dependency rules are
 in .d files that I then -include into the makefile. See the code
 example below. It seems this -include throws make off somehow so it
 doesn't issue any error messages. However, when I put the dependencies
 explicitly into the makefile, make tells me *** No rule to make
 target `doesnt_exist.h', needed by `test.o'. Stop., so that seems to
 be fine.

I tried it here.
With make 3.80 it works as expected. I do not have 3.81 handy right now.
Which version of make did you use?

Sam


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Make Error

[Ko Ken]

Description
Keywords: GNU, 3.8, bash

After I upgraded my Cygwin install to the latest make (3.81), it caused 
problems with the XPS make. When I try to Export to Project Navigator, the 
following error occurs:

ublaze_top.make:146: *** target pattern contains no `%'. Stop.


Solution
This error is probably due to an unsupported version of the make utility in 
the Cygwin installation. EDK provides the flexibility for users to use a 
pre-existing Cygwin environment (this is mostly a Cygwin installation that the 
user installed outside of the EDK installation). The latest version (v3.81) of 
the make utility is known to have problems related to path references. This 
version of the make utility is not supported by EDK. The make utility that 
ships with EDK is of version v3.79.1 and is a supported version.

To determine the version of the make utility being used, launch an EDK shell 
(from the Start Menu or from the XPS environment), and use the command, make 
-v. See sample output below:

$ make -v
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 i686-pc-cygwin


If the above message occurs, this version of the make utility is not 
supported. The make utility that ships with EDK produces the following output:

$ make -v
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000
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.

Report bugs to bug-make@gnu.org.


To fix the problem, you can perform one of the following:

- Uninstall the current Cygwin installation and then install the EDK Cygwin:
1. Backup the existing Cygwin registry branches if they will later be needed by 
Exporting them from Registry Editor:
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2
2. Delete both branches.
3. Launch the EDK shell. The Registry is automatically populated with entries 
from the Cygwin in the EDK installation area.

- Make a backup of the make.exe in the existing Cygwin installation (under 
the /bin directory). Copy the make.exe utility from EDK Cygwin installation 
(%Xilinx_EDK%\cygwin\bin) to the Cygwin installation's bin directory. 

NOTE: Refer to (Xilinx Answer 24134) for more options. 



  



___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

Re: Make Error

[Brian Dessent]

Ko Ken wrote:

 After I upgraded my Cygwin install to the latest make (3.81), it caused 
 problems with the XPS make. When I try to Export to Project Navigator, the 
 following error occurs:
 
 ublaze_top.make:146: *** target pattern contains no `%'. Stop.

I don't understand what you are asking or reporting.  This is not a bug,
more like an expression of the fact that the Cygwin project doesn't
generally support using paths with drive letters, i.e. Win32 style
paths, because Cygwin tries to provide a *nix-like environment.  It has
been discussed to death on the Cygwin mailing list and to a lesser
degree on the make-w32 mailing list.  There is a workaround implemented
in CVS HEAD.

 This error is probably due to an unsupported version of the make utility in 
 the 
 [snip directions]

So, it seems you have your solution.  What's the question?

Brian


___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

make error

[Tracy Chang]

Hi,
I got this message when I am building an image.  

 -t, --touch Touch targets instead of remaking them.
 -v, --version   Print the version number of make and exit.
 -w, --print-directory   Print the current directory.
 --no-print-directoryTurn off -w, even if it was turned on 
implicitly.
 -W FILE, --what-if=FILE, --new-file=FILE, --assume-new=FILE
 Consider FILE to be infinitely new.
 --warn-undefined-variables  Warn when an undefined variable is referenced.

Report bugs to [EMAIL PROTECTED].
make: *** [allcommonlego] Error 2
Tracy

___
Bug-make mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-make

Re: make error

[Paul D. Smith]

There must be more to this message, printed before this.

It looks like you're invoking GNU make with some invalid command-line
options and it's printing the help and exiting.  To know what the error
is you'd have to look up _before_ the help is printed and see how you're
invoking make and also what the error message was.

-- 
---
 Paul D. Smith [EMAIL PROTECTED]  Find some GNU make tips at:
 http://www.gnu.org  http://make.paulandlesley.org
 Please remain calm...I may be mad, but I am a professional. --Mad Scientist


___
Bug-make mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-make

Make error

[spai]

I like the idea of using implicit rules
to do all the work. With that objective, is there an elegant
way to do than doing it as follow:
bld_dir = ../obj
$(bld_dir)/%.o: %.cpp
$(COMPILE.cpp)
$(OUTPUT_OPTION) $
The above rule above creates all the object files in ../obj
directory.
However using:
$(bin_dir)/%: %.cpp
$(LINK.cpp)
$^ $(LOADLIBES) $(LDLIBS) -o $@
gives the following error.
gnumake: *** No rule to make target
`../bin/OneLevel_OneGlobal_SASD', needed by `build'. Stop.
The full makefile is shown below.
# $Source$
# 
SYSTEMC = /prj/vlsi/scp/osci/systemc-2.0.1
bin_dir = ../bin
# Set the default variables 
CC = g++
CXXFLAGS = -g -Wall -Wno-deprecated
TARGET_ARCH = 
CPPFLAGS = -I$(SYSTEMC)/include \

-I../axi
#Libraries: 
LDFLAGS=-g
LDLIBS = \
-L../lib
-lqctaxicore \
-L$(SYSTEMC)/lib-gccsparcOS5
-lsystemc -lm 
target_bus_models = \
 OneLevel_OneGlobal_SASD.cpp

# Executables
TARGETS = $(target_bus_models:%.cpp=$(bin_dir)/%)
$(bin_dir)/%: %.cpp
$(LINK.cpp)
$^ $(LOADLIBES) $(LDLIBS) -o $@
# Build all targets
build: $(TARGETS)
# Clean directory
clean:
rm -rf
$(TARGETS)






___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

Re: make error

[spai]

At 09:27 PM 11/17/2003 -0500, Paul D. Smith wrote:
Please check the GNU make manual for information on make syntax.

In particular, every shell command line in a make rule must begin with a
TAB character (not spaces, but a TAB).
Ahhh, didn't know about this rule for the shell command. Others worked
okay without having a tab in front of them.
Thanks a lot,
Suhas

--
---
 Paul D. Smith [EMAIL PROTECTED]  Find some GNU make tips at:
 http://www.gnu.org  http://make.paulandlesley.org
 Please remain calm...I may be mad, but I am a professional. --Mad 
Scientist




___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

Re: make error

[Paul D. Smith]

Please check the GNU make manual for information on make syntax.

In particular, every shell command line in a make rule must begin with a
TAB character (not spaces, but a TAB).

-- 
---
 Paul D. Smith [EMAIL PROTECTED]  Find some GNU make tips at:
 http://www.gnu.org  http://make.paulandlesley.org
 Please remain calm...I may be mad, but I am a professional. --Mad Scientist


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

make error with pro*c redhat 7.2

[Guy L]

Hello, 

getting this error while using make with the 
precompiler Pro*C (linux Redhat 7.2).
GNU Make version 3.79.1
Here is the error:
[make] : *** [sample9.o] segmentation 
fault

How to fix that


Thank a lot

Guy L.

___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

RE: make error with pro*c redhat 7.2

[lasse.makholm]

From http://www.gnu.org/manual/make-3.79.1/html_mono/make.html#SEC124 :

`[foo] signal description' 
These errors are not really make errors at all. They mean that a program that make 
invoked as part of a command script returned a non-0 error code (`Error NN'), which 
make interprets as failure, or it exited in some other abnormal fashion (with a signal 
of some type). See section Errors in Commands. If no *** is attached to the message, 
then the subprocess failed but the rule in the makefile was prefixed with the - 
special character, so make ignored the error. 


So this is not a make problem but probably a compiler problem...

/Lasse

-Original Message-
From: ext Guy L [mailto:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 1:26 PM
To: [EMAIL PROTECTED]
Subject: make error with pro*c redhat 7.2


Hello, 

getting this error while using make with the precompiler Pro*C (linux Redhat 7.2).
GNU Make version 3.79.1
Here is the error:
[make] : *** [sample9.o] segmentation fault

How to fix that


Thank a lot

Guy L.


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

Re: make error with pro*c redhat 7.2

[Paul D. Smith]

%% Guy L [EMAIL PROTECTED] writes:

  gl getting this error while using make with the precompiler Pro*C (linux
  gl Redhat 7.2).

  gl GNU Make version 3.79.1

  gl Here is the error:
  gl [make] : *** [sample9.o] segmentation fault
 
This means your compiler dumped core.  Try running the command that make
printed directly from the shell and you'll probably find it does the
same thing.

This is not a make issue; please contact your compiler vendor.
 
-- 
---
 Paul D. Smith [EMAIL PROTECTED]  Find some GNU make tips at:
 http://www.gnu.org  http://make.paulandlesley.org
 Please remain calm...I may be mad, but I am a professional. --Mad Scientist


___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

make error...can not create ar

[Richard Dunham]

# make ar
/opt/SUNWspro/bin/cc -gar.c   -o ar
./make.h, line 28: cannot find include file: config.h
cc: acomp failed for ar.c
make: *** [ar] Error 2
#   

Try again using modified make.h with config.h

# make ar
/opt/SUNWspro/bin/cc -gar.c   -o ar
Undefined   first referenced
 symbol in file
alpha_compare   ar.o
perror_with_namear.o
ar_member_touch ar.o
lookup_file ar.o
enter_file  ar.o
file_exists_p   ar.o
ar_name_equal   ar.o
error   ar.o
savestring  ar.o
f_mtime ar.o
xmalloc ar.o
main/opt/SUNWspro/WS6U1/lib/crt1.o
ar_scan ar.o
fatal   ar.o
concat  ar.o
ld: fatal: Symbol referencing errors. No output written to ar
make: *** [ar] Error 1
#
  
# make 
make  all-recursive
make[1]: Entering directory `/usr/local/src/make-3.79.1'
Making all in glob
make[2]: Entering directory `/usr/local/src/make-3.79.1/glob'
/opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I. -I.. -g -c glob.c
/opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I. -I.. -g -c fnmatch.c
rm -f libglob.a
ar cru libglob.a glob.o fnmatch.o
make[2]: ar: Command not found
make[2]: *** [libglob.a] Error 127
make[2]: Leaving directory `/usr/local/src/make-3.79.1/glob'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/make-3.79.1'
make: *** [all-recursive-am] Error 2

# sh ./build.sh
compiling ar.c...
compiling arscan.c...
compiling commands.c...
compiling dir.c...
compiling expand.c...
compiling file.c...
compiling function.c...
compiling getopt.c...
compiling implicit.c...
compiling job.c...
compiling main.c...
compiling misc.c...
compiling read.c...
compiling remake.c...
compiling rule.c...
compiling signame.c...
compiling variable.c...
compiling vpath.c...
compiling default.c...
compiling version.c...
compiling getopt1.c...
compiling remote-stub.c...
compiling gettext.c...
compiling glob/fnmatch.c...
compiling glob/glob.c...
linking make...
done
#


#  Makefile ###
# Generated automatically from Makefile.in by configure.
# Makefile.in generated automatically by automake 1.4 from Makefile.am

# Copyright (C) 1994, 1995-8, 1999 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.

# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.

# This is a -*-Makefile-*-, or close enough


SHELL = /bin/sh

srcdir = .
top_srcdir = .
prefix = /usr/local
exec_prefix = ${prefix}

bindir = ${exec_prefix}/bin
sbindir = ${exec_prefix}/sbin
libexecdir = ${exec_prefix}/libexec
datadir = ${prefix}/share
sysconfdir = ${prefix}/etc
sharedstatedir = ${prefix}/com
localstatedir = ${prefix}/var
libdir = ${exec_prefix}/lib
infodir = ${prefix}/info
mandir = ${prefix}/man
includedir = ${prefix}/include
oldincludedir = /usr/include

DESTDIR =

pkgdatadir = $(datadir)/make
pkglibdir = $(libdir)/make
pkgincludedir = $(includedir)/make

top_builddir = .

ACLOCAL = /usr/local/src/make-3.79.1/missing aclocal
AUTOCONF = /usr/local/src/make-3.79.1/missing autoconf
AUTOMAKE = /usr/local/src/make-3.79.1/missing automake
AUTOHEADER = /usr/local/src/make-3.79.1/missing autoheader

INSTALL = ./install-sh -c
INSTALL_PROGRAM = ${INSTALL} $(AM_INSTALL_PROGRAM_FLAGS)
INSTALL_DATA = ${INSTALL} -m 644
INSTALL_SCRIPT = ${INSTALL_PROGRAM}
transform = s,x,x,

NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
host_alias = sparc-sun-solaris2.8
host_triplet = sparc-sun-solaris2.8
ALL_LINGUAS = de es fr ja ko nl pl pt_BR ru
ALL_MOFILES =  de.mo es.mo fr.mo ja.mo ko.mo nl.mo pl.mo pt_BR.mo ru.mo
ALL_POFILES =  de.po es.po fr.po ja.po ko.po nl.po pl.po pt_BR.po ru.po
AR = ar
CC = /opt/SUNWspro/bin/cc
CPP = /opt/SUNWspro/bin/cc -E
GETCONF = getconf
GLOBDIR = glob
GLOBINC = -I$(srcdir)/glob
GLOBLIB = glob/libglob.a
LIBOBJS =  gettext.o
MAKEINFO = /usr/local/src/make-3.79.1/missing makeinfo
MOFILES =  de.mo es.mo fr.mo ja.mo ko.mo nl.mo pl.mo pt_BR.mo ru.mo
PACKAGE = make
PERL = perl
RANLIB = :
REMOTE = stub
VERSION = 3.79.1

AUTOMAKE_OPTIONS = 1.4

SUBDIRS = $(GLOBDIR) i18n

bin_PROGRAMS = make

# These source files also have gettext references
SRCS = ar.c arscan.c commands.c dir.c expand.c file.c
function.cgetopt.c
implicit.c job.c main.c misc.c read.c 

Re: make error...can not create ar

[Paul D. Smith]

%% Regarding make error...can not create ar ; you wrote:

  rd # make ar
  rd /opt/SUNWspro/bin/cc -gar.c   -o ar

You can't make it because ar is a system utility (the library archive
creator, the thing that creates libXXX.a files).  It is not a part of
GNU make.

  rd make[2]: ar: Command not found

This means that make can't find the ar program, which you must make
available to build GNU make.

On Solaris, these tools are kept in the strange and unusual
/usr/ccs/bin, so make sure that directory is in your $PATH variable.

-- 
---
 Paul D. Smith [EMAIL PROTECTED]  Find some GNU make tips at:
 http://www.gnu.org  http://www.paulandlesley.org/gmake/
 Please remain calm...I may be mad, but I am a professional. --Mad Scientist

___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make

Re: make error...can not create ar

[Richard Dunham]

Thank you...it worked like a champ.

Richard


Paul D. Smith wrote:
 
 %% Regarding make error...can not create ar ; you wrote:
 
   rd # make ar
   rd /opt/SUNWspro/bin/cc -gar.c   -o ar
 
 You can't make it because ar is a system utility (the library archive
 creator, the thing that creates libXXX.a files).  It is not a part of
 GNU make.
 
   rd make[2]: ar: Command not found
 
 This means that make can't find the ar program, which you must make
 available to build GNU make.
 
 On Solaris, these tools are kept in the strange and unusual
 /usr/ccs/bin, so make sure that directory is in your $PATH variable.
 
 --
 ---
  Paul D. Smith [EMAIL PROTECTED]  Find some GNU make tips at:
  http://www.gnu.org  http://www.paulandlesley.org/gmake/
  Please remain calm...I may be mad, but I am a professional. --Mad Scientist

___
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make