steve-

you're right.  if you link ./gmond/machines/linux.c to ./gmond/machine.c 
then the compile with hop along as it should.  

we are close to releasing 2.5.0 (in the next week or so).  it's in the CVS 
tree for ganglia.. you might want to take a look at it.

-matt

Today, Steven A. DuChene wrote forth saying...

> I am trying to build an ia64 rpm of our the 2.2.3 version of 
> ganglia-monitor-core
> for the OSCAR tool suite distribution and I am getting an error that I 
> "believe"
> is due to a build script/layout problem.
> 
> make[3]: Leaving directory 
> `/usr/src/redhat/BUILD/ganglia-monitor-core-2.2.3/gmond/gstat'
> make[3]: Entering directory 
> `/usr/src/redhat/BUILD/ganglia-monitor-core-2.2.3/gmond'
> gcc -DHAVE_CONFIG_H -I. -I. -I..    -I../lib -O2  -D_REENTRANT -Wall -Wshadow 
> -Wpointer-arith -Wcast-align -Wstrict-prototypes -c machine.c
> cpp0: machine.c is a directory
> make[3]: *** [machine.o] Error 1
> 
> Now in ./gmond/ of the source tree there is a link:
> 
> [EMAIL PROTECTED] ganglia-monitor-core-2.2.3]# ll gmond/
> total 192
> -rw-r--r--    1 root     root        13946 Apr  8 15:47 cmdline.c
> -rw-r--r--    1 root     root         3114 Apr  8 15:46 cmdline.h
> -rw-r--r--    1 root     root         4692 Apr  8 15:48 gmond.c
> -rw-r--r--    1 root     root        13320 Aug 23 13:56 gmond.o
> drwxr-xr-x    3 root     root         4096 Aug 23 13:56 gstat
> -rw-r--r--    1 root     root          625 Nov  4  2001 key_metrics.h
> -rw-r--r--    1 root     root        18120 Apr  8 15:23 listen.c
> -rw-r--r--    1 root     root        21312 Aug 23 13:56 listen.o
> lrwxrwxrwx    1 root     root           20 Aug 23 13:56 machine.c -> 
> .././gmond/machines/
> drwxr-xr-x    2 root     root         4096 Apr  8 15:31 machines
> -rw-r--r--    1 root     root        14353 Aug 23 13:56 Makefile
> -rw-r--r--    1 root     root          393 Apr  4 14:29 Makefile.am
> -rw-r--r--    1 root     root        14135 Apr  8 16:09 Makefile.in
> -rw-r--r--    1 root     root         4226 Apr  4 12:16 metric.h
> -rw-r--r--    1 root     root         1484 Mar  7 17:10 metric_typedefs.h
> -rw-r--r--    1 root     root         6896 Feb  1  2002 monitor.c
> -rw-r--r--    1 root     root        11416 Aug 23 13:56 monitor.o
> -rw-r--r--    1 root     root          531 Mar  7 17:09 node_data_t.h
> -rw-r--r--    1 root     root         6512 Apr  4 18:00 server.c
> -rw-r--r--    1 root     root        10808 Aug 23 13:56 server.o
> 
> The same directory on an ia32 system looks like:
> 
> [EMAIL PROTECTED] ganglia-monitor-core-2.2.3]# ll gmond/
> total 192
> -rw-r--r--    1 root     root        13946 Apr  8 15:47 cmdline.c
> -rw-r--r--    1 root     root         3114 Apr  8 15:46 cmdline.h
> -rw-r--r--    1 root     root         4692 Apr  8 15:48 gmond.c
> -rw-r--r--    1 root     root        13320 Aug 23 13:56 gmond.o
> drwxr-xr-x    3 root     root         4096 Aug 23 13:56 gstat
> -rw-r--r--    1 root     root          625 Nov  4  2001 key_metrics.h
> -rw-r--r--    1 root     root        18120 Apr  8 15:23 listen.c
> -rw-r--r--    1 root     root        21312 Aug 23 13:56 listen.o
> lrwxrwxrwx    1 root     root           20 Aug 23 13:56 machine.c -> 
> .././gmond/machines/
> drwxr-xr-x    2 root     root         4096 Apr  8 15:31 machines
> -rw-r--r--    1 root     root        14353 Aug 23 13:56 Makefile
> -rw-r--r--    1 root     root          393 Apr  4 14:29 Makefile.am
> -rw-r--r--    1 root     root        14135 Apr  8 16:09 Makefile.in
> -rw-r--r--    1 root     root         4226 Apr  4 12:16 metric.h
> -rw-r--r--    1 root     root         1484 Mar  7 17:10 metric_typedefs.h
> -rw-r--r--    1 root     root         6896 Feb  1  2002 monitor.c
> -rw-r--r--    1 root     root        11416 Aug 23 13:56 monitor.o
> -rw-r--r--    1 root     root          531 Mar  7 17:09 node_data_t.h
> -rw-r--r--    1 root     root         6512 Apr  4 18:00 server.c
> -rw-r--r--    1 root     root        10808 Aug 23 13:56 server.o
> 
> 
> Is this a known problem? Is there a work around?
> I see this "linking" takes place when the configure script is run.
> I'm assuming this is due to the unexpected ia64 in the host system type.
> 


Reply via email to