pthreads/dlopen issue when building krb-1.6.3 on AIX 6.1?

Luke Scharf luke.scharf at clusterbee.net
Wed May 13 12:16:47 EDT 2009


Awesome!  Editing shlib.conf did the trick, and I'm unstuck!

I do consider this a bug.  If you feel like submitting the report, that 
would save me the trouble of figuring out and signing up for an account 
on the bug tracking system.  If not, I'll be happy to be a good 
open-source citizen and submit it.

Thanks again!
-Luke

I'm still mucking with getting pthreads enabled properly, but I have a 
little bit more Googling to do before I can ask a proper question about 
that.


miguel.sanders at arcelormittal.com wrote:
> Luke
>
> You should take a look at the config/shlib.conf
> Apparently krb5-1.6.3 is not yet AIX6.1 aware.
> Just alter the *-*-aix5*) on line 410 to f.e. *-*-aix*)
>
> Should I file a bug report for this?
>
>
> Met vriendelijke groet
> Best regards
> Bien à vous
>
> Miguel SANDERS
> ArcelorMittal Gent
>
> UNIX Systems & Storage
> IT Supply Western Europe | John Kennedylaan 51
> B-9042 Gent
>
> T +32 9 347 3538 | F +32 9 347 4901 | M +32478 805 023
> E miguel.sanders at arcelormittal.com
> www.arcelormittal.com/gent
>
> -----Oorspronkelijk bericht-----
> Van: kerberos-bounces at mit.edu [mailto:kerberos-bounces at mit.edu] Namens Luke Scharf
> Verzonden: woensdag 13 mei 2009 17:17
> Aan: kerberos at mit.edu
> Onderwerp: pthreads/dlopen issue when building krb-1.6.3 on AIX 6.1?
>
> I'm attempting to build MIT Kerberos version 1.6.1 on AIX 6.1.  I'm mostly in need of the client libraries and utilities.
>
> I'm using the following special additions to the build environment:
>
>     $ export PTHREAD_LIBS="-lpthread"
>     $ export RPATH_FLAG="-Wl,-brtl,-blibpath:"
>
>
> I'm using the following ./configure command:
>
>     $ ./configure --prefix=/usr/local/krb5-1.6.3
>     --enable-log-preauth-logins --enable-login-print-issue
>     --with-multihomed-fixes --enable-app-proxy --with-passive-mode-off
>     --without-anonymous-ftp
>
>
> And I get the following results when I run it:
>
>     [snip]
>     configure: enabling thread support
>     checking for pthread_join in LIBS=-lpthread with CFLAGS=... yes
>     checking for joinable pthread attribute... unknown
>     configure: WARNING: we do not know how to create joinable pthreads
>     checking if more special flags are required for pthreads... -D_THREAD_SAFE
>     checking for cc_r... cc_r
>     configure: PTHREAD_CC = cc_r
>     configure: PTHREAD_CFLAGS = -D_THREAD_SAFE 
>     configure: PTHREAD_LIBS = -lpthread
>     checking for pthread_once... yes
>     checking for pthread_rwlock_init... yes
>     configure: rechecking with PTHREAD_... options
>     checking for pthread_rwlock_init in -lc... yes
>     checking for library containing dlopen... none required
>     checking keyutils.h usability... no
>     checking keyutils.h presence... no
>     checking for keyutils.h... no
>     configure: disabling static libraries
>     configure: WARNING: shared libraries not supported on this architecture
>     configure: error: must enable one of shared or static libraries
>     $
>
>
> Does anyone have any suggestions?
>
> Many thanks,
> -Luke
>
>
>
> ________________________________________________
> Kerberos mailing list           Kerberos at mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
>
> **** 
> This message and any attachment are confidential, intended solely for the use of the individual or entity to whom it is addressed and may be protected by professional secrecy or intellectual property rights. 
> If you have received it by mistake, or are not the named recipient(s), please immediately notify the sender and delete the message. You are hereby notified that any unauthorized use, copying or dissemination of any or all information contained in this message is prohibited. 
> Arcelormittal shall not be liable for the message if altered, falsified, or in case of error in the recipient. 
> This message does not constitute any right or commitment for ArcelorMittal except when expressly agreed otherwise in writing in a separate agreement.  
> ****  
>   




More information about the Kerberos mailing list