[GE users] UNSUPPORTED-lx26-GLIBC-2.8-amd64

Rayson Ho rayrayson at gmail.com
Mon Sep 22 18:25:59 BST 2008


    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "ISO-8859-10" character set.  ]
    [ Some special characters may be displayed incorrectly. ]

On 9/22/08, Sean Davis <sdavis2 at mail.nih.gov> wrote:
> So, it appears that the arch script does not believe that glibc-2.8 is
> supported.  There is support for 2.[3-6]*.  Any reason not to edit the
> arch script to include through 2.8?

Basically, the SGE developers believe that if an OS version is not
tested, then it is unsupported. It is true sometimes, as early glibc
versions did not offer backward compatibility.

However, newer glibc versions do offer better backward compatibility,
and I remember hacking the arch script to relax the glibc version
check a bit a year or 2 ago when I was encountering the same problem,
and it worked well.

You can either hack the arch script and make it support glibc 2.8, and
do some testing. Or, you can compile your execd natively on the
machine to be 100% sure that glibc backward compatibility won't be an
issue.

Rayson


>
> Here is the relevant section from arch script, it seems:
>
> ------------------------------------
>      # verify the GNU C lib version
>      # For an alternative means to determine GNU C lib version see
>      # http://www.gnu.org/software/libc/FAQ.html#s-4.9
>      case $lxmachine in
>      amd64)
>         libc=`/lib64/libc.so.6 2>/dev/null | head -1`
>         ;;
>      ia64)
>         libc=`/lib/libc.so.6.1 2>/dev/null | head -1`
>         ;;
>      *)
>         libc=`/lib/libc.so.6 2>/dev/null | head -1`
>         ;;
>      esac
>      libc=`echo $libc | sed -e 's/^.*version//'`
>      libc=`echo $libc | cut -d ' ' -f1`
>
>      case $libc in
>      2.2*)
>         unsupported="u"
>         ;;
>      2.[3-6]*)
>         ;;
>      *)
>         unsupported="UNSUPPORTED-"
>         lxrelease=${lxrelease}-GLIBC-${libc}
>      esac
> -------------------------------
>
> Thanks,
> Sean
>
>
> >>> On 9/22/08, Sean Davis <sdavis2 at mail.nih.gov> wrote:
> >>>>
> >>>> I am trying to install execd (6.2b1) services on a new machine.  The
> >>>> install_execd script complains:
> >>>>
> >>>> # ./install_execd
> >>>> Architecture UNSUPPORTED-lx26-GLIBC-2.8-amd64 not supported by this
> >>>> procedure!
> >>>>
> >>>> # uname -a
> >>>> Linux Grass 2.6.25.16-0.1-default #1 SMP 2008-08-21 00:34:25 +0200
> >>>> x86_64 x86_64 x86_64 GNU/Linux
> >>>>
> >>>> Any suggestions?
> >>>>
> >>>> Thanks,
> >>>> Sean
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> >>>> For additional commands, e-mail: users-help at gridengine.sunsource.net
> >>>>
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> >>> For additional commands, e-mail: users-help at gridengine.sunsource.net
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> >> For additional commands, e-mail: users-help at gridengine.sunsource.net
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
> For additional commands, e-mail: users-help at gridengine.sunsource.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe at gridengine.sunsource.net
For additional commands, e-mail: users-help at gridengine.sunsource.net




More information about the gridengine-users mailing list