Sorry, my mistake. The config.h file shouldn't be there at all. It was
left over from the opensolaris version. With the SourceForge version
config.h is generated by the "configure" script. Just remove it before
running "configure".
This may not solve all the problems, but it might reduce them. Let me
know which ones are left, please.
Drew
On Jun 8, 2009, at 2:56 PM, Demetri S. Mouratis wrote:
Drew,
Thanks for the pointer. Here's what I have so far for the Linux
problems:
Problem 1:
I think that HAVE_BOOLEAN_T is wrong because the distribution
tarball has a filebench/config.h with "#define HAVE_BOOLEAN_T 1" in
it. I whacked that, re-ran configure, and it seems to use the one
in the top-level directory. Was that supposed to be there?
Problem 2:
In filebench/multi_client_sync.h: My distribution seems to need
#include <netinet/ip.h> (instead of inet/ip.h). I don't know how
you like to #ifdef OS-specific stuff.
Problem 3:
multi_client_sync.c for Linux wants an extra parameter to
gethostbyname_r. Here are my diffs:
48a49,50
struct hostent *master_result;
69c71
< &error_num) == NULL) {
---
&master_result, &error_num) == NULL) {
Problem 4:
parser_gram.y: In function 'parser_fscheck':
parser_gram.y:3597: error: 'FSTYPSZ' undeclared (first use in this
function)
parser_gram.y:3597: error: (Each undeclared identifier is reported
only once
parser_gram.y:3597: error: for each function it appears in.)
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3597: error: 'struct statvfs64' has no member named
'f_basetype'
parser_gram.y:3600: error: 'struct statvfs64' has no member named
'f_basetype'
I don't know to fix that one, and could use a hand. :-(
...Demetri
--
This message posted from opensolaris.org
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
