SELinux compile errors

SELinux compile errors

[Subba Rao]

Hi

I am trying to compile SELinux on Slackware 8.1
The LSM tree is LSM-2.4-selinux-2002102211.tgz.  I have downloaded the complete source tree. 

Towards the end of the kernel compilation I got the following error messages:

===========================================================
make[3]: Entering directory `/usr/src/lsm-2.4/security/selinux/flask'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/usr/src/lsm-2.4/security/selinux/flask'
make -C selopt
make[3]: Entering directory `/usr/src/lsm-2.4/security/selinux/selopt'
gcc -D__KERNEL__ -I/usr/src/lsm-2.4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-commo
 -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=k6    -I../include -I.. -nostdinc -I /usr/lib/gcc-lib/i3
6-slackware-linux/2.95.3/include -DKBUILD_BASENAME=selopt_core  -c -o selopt_core.o selopt_core.c
selopt_core.c: In function `selopt_ip_label_output':
selopt_core.c:299: parse error before `)'
selopt_core.c: In function `selopt_ip_map_input':
selopt_core.c:355: parse error before `)'
selopt_core.c:363: parse error before `)'
selopt_core.c: In function `selopt_ip_defragment':
selopt_core.c:549: parse error before `)'
make[3]: *** [selopt_core.o] Error 1
make[3]: Leaving directory `/usr/src/lsm-2.4/security/selinux/selopt'
make[2]: *** [_subdir_selopt] Error 2
make[2]: Leaving directory `/usr/src/lsm-2.4/security/selinux'
make[1]: *** [_subdir_selinux] Error 2
make[1]: Leaving directory `/usr/src/lsm-2.4/security'
make: *** [_dir_security] Error 2
===========================================================

Did anyone here on the list compile SELinux on Slackware 8.x successfully?

Subba Rao
sailorn@attglobal.net
2002-11-16



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux compile errors

[Kerry Thompson]

The same problem was raised a few weeks ago, it comes from ip_warn() in 
selopt_core.c having two arguments, while the macro definition in selopt.h 
has 3 arguments. Namely :



Can you please identify which GCC compiler you're using ( 'gcc --version' ) ?

Kerry


On Sun, 17 Nov 2002 04:58, Subba Rao wrote:
> Hi
>
> I am trying to compile SELinux on Slackware 8.1
> The LSM tree is LSM-2.4-selinux-2002102211.tgz.  I have downloaded the
> complete source tree.
>
> Towards the end of the kernel compilation I got the following error
> messages:
>
> ===========================================================
> make[3]: Entering directory `/usr/src/lsm-2.4/security/selinux/flask'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/usr/src/lsm-2.4/security/selinux/flask'
> make -C selopt
> make[3]: Entering directory `/usr/src/lsm-2.4/security/selinux/selopt'
> gcc -D__KERNEL__ -I/usr/src/lsm-2.4/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-commo -fomit-frame-pointer
> -pipe -mpreferred-stack-boundary=2 -march=k6    -I../include -I.. -nostdinc
> -I /usr/lib/gcc-lib/i3 6-slackware-linux/2.95.3/include
> -DKBUILD_BASENAME=selopt_core  -c -o selopt_core.o selopt_core.c
> selopt_core.c: In function `selopt_ip_label_output':
> selopt_core.c:299: parse error before `)'
> selopt_core.c: In function `selopt_ip_map_input':
> selopt_core.c:355: parse error before `)'
> selopt_core.c:363: parse error before `)'
> selopt_core.c: In function `selopt_ip_defragment':
> selopt_core.c:549: parse error before `)'
> make[3]: *** [selopt_core.o] Error 1
> make[3]: Leaving directory `/usr/src/lsm-2.4/security/selinux/selopt'
> make[2]: *** [_subdir_selopt] Error 2
> make[2]: Leaving directory `/usr/src/lsm-2.4/security/selinux'
> make[1]: *** [_subdir_selinux] Error 2
> make[1]: Leaving directory `/usr/src/lsm-2.4/security'
> make: *** [_dir_security] Error 2
> ===========================================================
>
> Did anyone here on the list compile SELinux on Slackware 8.x successfully?
>
> Subba Rao
> sailorn@attglobal.net
> 2002-11-16


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux compile errors

[Kerry Thompson]

Aaarg. Sorry about the previous broken message, it seems that CTRL-V in KMail 
is 'Send', and not 'Paste bit of useful code'.

The same problem was raised a few weeks ago, it comes from ip_warn() in 
selopt_core.c having two arguments, while the macro definition in selopt.h 
has 3 arguments. Namely :

in selopt.h :

  #define ip_warn(iph, fmt, args...)                                     \
       do { printk(KERN_WARNING "%s: " fmt, __FUNCTION__, ##args);     \
            printk(" [%u.%u.%u.%u->%u.%u.%u.%u]\n",                    \
            NIPQUAD(iph->saddr), NIPQUAD(iph->daddr));                 \
       } while (0);

while the lines in selopt_core.c with compiler warnings are like :

    ip_warn(iph, "out of memory expanding skb\n");

... and your compiler is having a nasty reaction to it. You could try adding 
an extra parameter to the ip_warn() calls, like adding a NULL argument. Or, 
you could avoid the issue by building without labelled network support in 
your kernel config and avoiding selopt altogether.

Can you please identify which GCC compiler you're using ( 'gcc --version' ) ?

Kerry


On Sun, 17 Nov 2002 04:58, Subba Rao wrote:
> Hi
>
> I am trying to compile SELinux on Slackware 8.1
> The LSM tree is LSM-2.4-selinux-2002102211.tgz.  I have downloaded the
> complete source tree.
>
> Towards the end of the kernel compilation I got the following error
> messages:
>
> ===========================================================
> make[3]: Entering directory `/usr/src/lsm-2.4/security/selinux/flask'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory `/usr/src/lsm-2.4/security/selinux/flask'
> make -C selopt
> make[3]: Entering directory `/usr/src/lsm-2.4/security/selinux/selopt'
> gcc -D__KERNEL__ -I/usr/src/lsm-2.4/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-commo -fomit-frame-pointer
> -pipe -mpreferred-stack-boundary=2 -march=k6    -I../include -I.. -nostdinc
> -I /usr/lib/gcc-lib/i3 6-slackware-linux/2.95.3/include
> -DKBUILD_BASENAME=selopt_core  -c -o selopt_core.o selopt_core.c
> selopt_core.c: In function `selopt_ip_label_output':
> selopt_core.c:299: parse error before `)'
> selopt_core.c: In function `selopt_ip_map_input':
> selopt_core.c:355: parse error before `)'
> selopt_core.c:363: parse error before `)'
> selopt_core.c: In function `selopt_ip_defragment':
> selopt_core.c:549: parse error before `)'
> make[3]: *** [selopt_core.o] Error 1
> make[3]: Leaving directory `/usr/src/lsm-2.4/security/selinux/selopt'
> make[2]: *** [_subdir_selopt] Error 2
> make[2]: Leaving directory `/usr/src/lsm-2.4/security/selinux'
> make[1]: *** [_subdir_selinux] Error 2
> make[1]: Leaving directory `/usr/src/lsm-2.4/security'
> make: *** [_dir_security] Error 2
> ===========================================================
>
> Did anyone here on the list compile SELinux on Slackware 8.x successfully?
>
> Subba Rao
> sailorn@attglobal.net
> 2002-11-16


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

SELinux compile errors

[Subba Rao]

Hello again

I have reinstalled Slackware 8.1 from scratch so that I have the default libraries to install SELinux.
The source tree I have used is lsm-2-4-selinux-2002102211.tgz  (option 1)  (When I extract I get "lsm-2.4" and "selinux"
directories)

The following are the sequence of steps I have followed to get compile SELinux

cd selinux/module
make insert
cd ../..

cd lsm-2.4
make menuconfig (configured my kernel)
make dep
make
make modules
make install
make modules_install

cd ../selinux
cd modules
make install

cd ../policy
vi users (deleted the example users and added my userid to the list)
make install-src install

cd ..
cd libsecure
make
make install

cd ..
cd utils
make


This is where I have stopped since I get the following error message:

--------------------------------------
make -C newrole
make[1]: Entering directory `/usr/src/selinux/utils/newrole'
cc -L/usr/local/selinux/lib -Wall -I/usr/local/selinux/include -DUSE_PAM -O3 -o newrole newrole.c -ldl -lpam -lpam_misc -lsecure
newrole.c:132: security/pam_appl.h: No such file or directory
newrole.c:133: security/pam_misc.h: No such file or directory
make[1]: *** [newrole] Error 1
make[1]: Leaving directory `/usr/src/selinux/utils/newrole'
make: *** [xnewrole] Error 2
--------------------------------------

It looks like it is looking for PAM library.

Can someone please let me know how to get over this error.  Yesterday after I installed PAM, this message went away, but then I was prompted for Kerberos and later for BSD library.  Russell did mention that there is no need for Kerberos, so this time I am stopping before having to install PAM.  I am using Slackware 8.1 distro.
 
Thank you in advance for any help.

Subba Rao
sailorn@attglobal.net
2002-11-29



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux compile errors

[Russell Coker]

On Fri, 29 Nov 2002 22:21, Subba Rao wrote:
> This is where I have stopped since I get the following error message:
>
> --------------------------------------
> make -C newrole
> make[1]: Entering directory `/usr/src/selinux/utils/newrole'
> cc -L/usr/local/selinux/lib -Wall -I/usr/local/selinux/include -DUSE_PAM
> -O3 -o newrole newrole.c -ldl -lpam -lpam_misc -lsecure newrole.c:132:
> security/pam_appl.h: No such file or directory
> newrole.c:133: security/pam_misc.h: No such file or directory
> make[1]: *** [newrole] Error 1
> make[1]: Leaving directory `/usr/src/selinux/utils/newrole'
> make: *** [xnewrole] Error 2
> --------------------------------------
>
> It looks like it is looking for PAM library.
>
> Can someone please let me know how to get over this error.  Yesterday after
> I installed PAM, this message went away, but then I was prompted for

You need PAM support and therefore you need the PAM header files and libraries 
installed.

> Kerberos and later for BSD library.  Russell did mention that there is no
> need for Kerberos, so this time I am stopping before having to install PAM.
>  I am using Slackware 8.1 distro.

Install PAM, then show us the error messages.

-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux compile errors

[Subba Rao]

I will first try the SSH without the kerberos option.  If it works then I will  file a bug report for Slackware.

Thank you.

Subba Rao
sailorn@attglobal.net
2002-11-30


======= At 2002-11-30, 17:58:00 you wrote: =======

>On Sat, 30 Nov 2002 17:45, Subba Rao wrote:
>> /usr/include/bits/string2.h:446: warning: pointer of type `void *' used in
>> arithmetic /usr/include/bits/string2.h:448: warning: pointer of type `void
>> *' used in arithmetic /usr/include/bits/string2.h:453: warning: pointer of
>> type `void *' used in arithmetic
>
>That looks like a bug in the string2.h file, but it might be a bug in 
>something else that it depends on.
>
>Does Slackware have a bug tracking system?  If so file a bug report about 
>this.
>
>> gcc -g -O2 -Wall -Wpointer-arith
>> -Wno-uninitialized -DWITH_SELINUX -I/usr/local/selinux/include -I. -I. 
>> -I/usr/kerberos/include -DSSHDIR=\"/etc/ssh\"
>> -D_PATH_SSH_PROGRAM=\"/usr/bin/ssh\"
>> -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/libexec/openssh/ssh-askpass\"
>> -D_PATH_SFTP_SERVER=\"/usr/libexec/openssh/sftp-server\"
>> -D_PATH_SSH_KEY_SIGN=\"/usr/libexec/openssh/ssh-keysign\"
>> -D_PATH_SSH_PIDDIR=\"/var/run\" -D_PATH_PRIVSEP_CHROOT_DIR=\"/var/empty\"
>> -DSSH_RAND_HELPER=\"/usr/libexec/openssh/ssh-rand-helper\" -DHAVE_CONFIG_H
>> -c monitor_wrap.c In file included from monitor_wrap.c:36:
>> auth.h:42: krb5.h: No such file or directory
>> make[1]: *** [monitor_wrap.o] Error 1
>> make[1]: Leaving directory `/usr/src/selinux/utils/openssh-3.4p1'
>> make: *** [xopenssh] Error 2
>>  --------------------------------------
>
>Have you tried adding --without-kerberos5 to the ./configure for ssh?
>
= = = = = = = = = = = = = = = = = = = =
			





--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux compile errors

[Jesse Pollard]

On Saturday 30 November 2002 11:03 am, Subba Rao wrote:
> I will first try the SSH without the kerberos option.  If it works then I
> will  file a bug report for Slackware.

It's not exactly a Slackware problem. They accept the configuration as defined 
by  the person making the submission.

Since you are doing a raw rebuild, you have to specify the "without-kerberos5"
and possibly "without-kerberos4" as well.

This is a leftover ? from adding kerberos support to OpenSSH by the OpenSSH
project. This was added only within the last 2/3 months, and the people using
it/developing it MUST have Kerberos included (Major Shared Resource Center
as part of the DoD HPC modernization program - me incuded as a user). I don't
know why it is on by default since it is useless without the path to the
Kerberos libraries. It may actually be a bug in the "configure" phase and not
a bug in the code.

> ======= At 2002-11-30, 17:58:00 you wrote: =======
>
> >On Sat, 30 Nov 2002 17:45, Subba Rao wrote:
> >> /usr/include/bits/string2.h:446: warning: pointer of type `void *' used
> >> in arithmetic /usr/include/bits/string2.h:448: warning: pointer of type
> >> `void *' used in arithmetic /usr/include/bits/string2.h:453: warning:
> >> pointer of type `void *' used in arithmetic
> >
> >That looks like a bug in the string2.h file, but it might be a bug in
> >something else that it depends on.
> >
> >Does Slackware have a bug tracking system?  If so file a bug report about
> >this.
> >
> >> gcc -g -O2 -Wall -Wpointer-arith
> >> -Wno-uninitialized -DWITH_SELINUX -I/usr/local/selinux/include -I. -I.
> >> -I/usr/kerberos/include -DSSHDIR=\"/etc/ssh\"
> >> -D_PATH_SSH_PROGRAM=\"/usr/bin/ssh\"
> >> -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/libexec/openssh/ssh-askpass\"
> >> -D_PATH_SFTP_SERVER=\"/usr/libexec/openssh/sftp-server\"
> >> -D_PATH_SSH_KEY_SIGN=\"/usr/libexec/openssh/ssh-keysign\"
> >> -D_PATH_SSH_PIDDIR=\"/var/run\"
> >> -D_PATH_PRIVSEP_CHROOT_DIR=\"/var/empty\"
> >> -DSSH_RAND_HELPER=\"/usr/libexec/openssh/ssh-rand-helper\"
> >> -DHAVE_CONFIG_H -c monitor_wrap.c In file included from
> >> monitor_wrap.c:36:
> >> auth.h:42: krb5.h: No such file or directory
> >> make[1]: *** [monitor_wrap.o] Error 1
> >> make[1]: Leaving directory `/usr/src/selinux/utils/openssh-3.4p1'
> >> make: *** [xopenssh] Error 2
> >>  --------------------------------------
> >
> >Have you tried adding --without-kerberos5 to the ./configure for ssh?
>
> = = = = = = = = = = = = = = = = = = = =

-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: SELinux compile errors

[Stephen D. Smalley]

SELinux isn't inherently dependent on PAM or kerberos.  If your system is not
using PAM, then you'll need to adjust the configure options in
utils/Makefile and the flags in the newrole and run_init Makefiles.
Likewise with the configure options for kerberos in utils/Makefile.

But I can't really recommend that you proceed down this path.  Porting
SELinux to Slackware properly requires more than just hacking up configure
options and Makefiles.

--
Stephen Smalley, NSA
sds@epoch.ncsc.mil


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.