Russ Allbery <[EMAIL PROTECTED]> writes:
> Brian May <[EMAIL PROTECTED]> writes:
>> Can I please confirm what version of Heimdal you are using? The initial
>> bug report seemed to quote the old version in testing, but here you
>> seem to indicate the latest version in unstable. I just want to make
>> sure.
>>
>> As far as I can tell, all exported symbols from libkrb5.24.0.0 use
>> HEIMDAL_KRB5_1.0 for the versioned symbol name.
> I'll check again tonight on amd64. The problem is specifically on
> amd64; if you're checking on i386, you may not see it. I wasn't seeing
> any symbol versioning in readelf.
Now I can't get valgrind to give me a backtrace. :/ It looks like it's
losing its file descriptor just before it would, and the report is
truncated. I'm not sure what would have changed to cause that; I remember
having to fiddle with it to get it to work the first time, but now I can't
reproduce the environment.
I can confirm that there's no symbol versioning, though; objdump -T shows
no versions on any of the symbols. And I know that causes problems, so
I'm pretty sure that's the issue still.
Checking the amd64 build logs, I see:
checking for ld --version-script... no
which is doubtless the problem. Here's a patch that looks like it should
work. After building Heimdal with this patch, I get symbol versions on
amd64.
--- heimdal-1.1/cf/version-script.m4.orig 2008-01-24 05:13:43.000000000
-0800
+++ heimdal-1.1/cf/version-script.m4 2008-04-28 20:28:39.000000000 -0700
@@ -16,7 +16,7 @@
int gss_init_creds(int foo) { return 0; }
EOF
- if AC_TRY_COMMAND([${CC-cc} $CFLAGS $LDFLAGS -shared
+ if AC_TRY_COMMAND([${CC-cc} $CFLAGS $LDFLAGS -fPIC -shared
-o conftest.so conftest.c
-Wl,--version-script,conftest.map]);
then
@@ -37,4 +37,4 @@
AM_CONDITIONAL(versionscript,test $doversioning = yes)
AC_SUBST(LDFLAGS_VERSION_SCRIPT)
-])
\ No newline at end of file
+])
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
