hotspot build problems

Andrew Haley aph at redhat.com
Fri Dec 10 16:53:00 UTC 2010


On 12/10/2010 04:45 PM, Volker Simonis wrote:
> Hi Per,
> 
> the SE stuff should already be handled by the Make process (as pointed
> out by Andrew). However I think the detection of SELinux is quite
> fragile, I also had problems with it in the past. In the build log you
> should see something like:
> 
>                                                 \
>             rm -f libjvm.so.1; ln -s libjvm.so libjvm.so.1;
>                       \
>             [ -f libjvm_g.so ] || { ln -s libjvm.so libjvm_g.so; ln -s
> libjvm.so.1 libjvm_g.so.1; };
> \
>             if [ \"\" = \"\" ] ; then                    \
>               if [ -x /usr/sbin/selinuxenabled ] ; then                 \
>                 /usr/sbin/selinuxenabled;                               \
>                 if [ $? = 0 ] ; then                                    \
>                   /usr/bin/chcon -t textrel_shlib_t libjvm.so;                 \
>                   if [ $? != 0 ]; then                                 \
>                     echo "ERROR: Cannot chcon libjvm.so";
>          \
>                   fi                                                    \
>                 fi                                                      \
>               fi                                                        \
>             fi                                                          \
>         }
> Linking vm...
> 
> If this fails, you'll have to work around it manually.

I'm not quite sure what all this code is for.  We could just unconditionally
execute

  /usr/bin/chcon -t textrel_shlib_t libjvm.so

and just generate a warning if it fails.

Andrew.



More information about the build-dev mailing list