On Nov 17, 2005, at 2:35 PM, Manfred Paul wrote:
...
[EMAIL PROTECTED]:~/Build/openafs-1.4.1-rc1$ ./configure --prefix /usr
--with-afs-sysname i386
AFAIK, i386 isn't a proper afs-sysname. That could explain the
missing param.h file.
[EMAIL PROTECTED]:~/Build/openafs-1.4.1-rc1$ export JAVA_HOME=/usr/lib/
j2se/1.4
[EMAIL PROTECTED]:~/Build/openafs-1.4.1-rc1$ make jafs
...
Now i moved into the src/JAVA/libjafs (for testing) and did:
[EMAIL PROTECTED]:~/Build/openafs-1.4.1-rc1/src/JAVA/libjafs$ make
...
make[1]: *** No rule to make target `/home/manfred/Build/
openafs-1.4.1-rc1/src/libuafs/UAFS/AFS_component_version_number.c',
needed by `/home/manfred/Build/openafs-1.4.1-rc1/src/libuafs/UAFS/
AFS_component_version_number.o'. Stop.
make[1]: Leaving directory `/home/manfred/Build/openafs-1.4.1-rc1/
src/JAVA/libjafs'
make: *** [libjafs] Error 2
What is the Problem?
-> `/home/manfred/Build/openafs-1.4.1-rc1/include/afs/param.h'.
does not exist - year that's true, but why?
see above ...
-> /home/manfred/Build/openafs-1.4.1-rc1/src/libuafs/UAFS/
AFS_component_version_number.c - this file is also missing
The ...version_number.c files should be generated by the build
process. If it's not there, take a closer look at what your
configure, make etc. did to that directory and whether it touched it
at all. (generating a new Makefile etc.)
Horst
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel