Re: Bacula on 1.92

Steve Blackwell <[email protected]>
Newsgroups gmane.linux.aurora.user
Message-ID <[email protected]>
Tom 'spot' Callaway wrote:

>On Sat, 2006-10-21 at 09:15 +0100, Steve Blackwell wrote:
>  
>
>>I am running aurora 1.92 on an ultra 5 and it has been running perfectly for 2 years now.
>>
>>I have just tried to compile/install Bacula 1.38.11 (client) on it and
>>have got the following error messages during the configure phase of the
>>compile.
>>
>>(These are an extract)
>>/usr/include/bits/socket.h:304:24: asm/socket.h: No such file or directory
>>In file included from /usr/include/sys/ioctl.h:27,
>>                from ../bacula.h:92,
>>                from console_conf.c:37:
>>/usr/include/bits/ioctls.h:24:24: asm/ioctls.h: No such file or directory
>>In file included from /usr/include/bits/ioctls.h:37,
>>                from /usr/include/sys/ioctl.h:27,
>>                from ../bacula.h:92,
>>                from console_conf.c:37:
>>/usr/include/linux/sockios.h:21:25: asm/sockios.h: No such file or directory
>>In file included from /usr/include/sys/ioctl.h:30,
>>                from ../bacula.h:92,
>>                from console_conf.c:37:
>>/usr/include/bits/ioctl-types.h:25:24: asm/ioctls.h: No such file or
>>directory
>>
>>I have tried # sparc32 bash before I compiled and I get the same result.
>>    
>>
>
>Eww. Userspace app using kernel headers.
>
>Your best bet here would be to get the Aurora 1.92 kernel SRPM, install
>it (rpm -ivh kernel*.src.rpm), then prep the tree (rpmbuild
>-bp /usr/src/redhat/SPECS/kernel*.spec), then go
>into /usr/src/redhat/BUILD/kernel-*/linux*/include/ and make a symlink
>from asm-sparc to asm. Last but not least, you'd want to add the
>following flag to the bacula compile string:
>
>-I/usr/src/redhat/BUILD/kernel-*/linux*/include/
>
>In that string, you want to replace the * with the actual values in the
>path, so it looks the same as when you type `pwd` in the include
>directory of the kernel source tree.
>
>Then, bacula should get past those errors. Of course, it might just as
>likely explode again, but its step one.
>
>In the next major Aurora build, we're going to have proper kernel
>headers in place for both sparc and sparc64, so this shouldn't be a
>problem.
>
>~spot
>  
>
I just tried the process as you suggested and I got the following error 
when I tried to rebuild the rpm.

+ echo 'Patch #10000 (linux-2.6.0-compile.patch):'
Patch #10000 (linux-2.6.0-compile.patch):
+ patch -p1 -s
+ cp /usr/src/redhat/SOURCES/COPYING.modules Documentation/
+ mkdir configs
+ cp -fv /usr/src/redhat/SOURCES/kernel-2.6.8-sparc64-smp.config 
/usr/src/redhat/SOURCES/kernel-2.6.8-sparc64.config .
`/usr/src/redhat/SOURCES/kernel-2.6.8-sparc64-smp.config' -> 
`./kernel-2.6.8-sparc64-smp.config'
`/usr/src/redhat/SOURCES/kernel-2.6.8-sparc64.config' -> 
`./kernel-2.6.8-sparc64.config'
+ mv kernel-2.6.8-sparc64-smp.config .config
++ echo kernel-2.6.8-sparc64-smp.config
++ cut -d- -f3
++ cut -d. -f1
++ sed -e s/i.86/i386/ -e s/s390x/s390/ -e s/ppc64.series/ppc64/
+ make ARCH=sparc64 nonint_oldconfig
In file included from /usr/include/sys/socket.h:35,
                 from /usr/include/netinet/in.h:24,
                 from /usr/include/arpa/inet.h:23,
                 from scripts/basic/fixdep.c:115:
/usr/include/bits/socket.h:304:24: asm/socket.h: No such file or directory
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.52457 (%prep)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.52457 (%prep)

This error message is very similar to the one I get when Bacula bails 
out during the configure stage.

I believe my problem is with the kernel headers, can any one give me 
some direction?

Cheers

Steve
_______________________________________________
Aurora-sparc-user mailing list
[email protected]
http://lists.auroralinux.org/mailman/listinfo/aurora-sparc-user
Aurora FAQ: http://www.ecs.soton.ac.uk/~mas01r/aurorafaq.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.