Actually, it turns out that just removing res_search causes
the RPM to fail to build on RHEL3.. So.. I think I need to
take this route and search for both res_search and __res_search.
I'm testing it now on EL3.. But then I suspect I'll have to go
back and rebuild FC1,3,4. Feh!
-derek
Russ
Hi Kevin!!
Kevin Coffman wrote:
Yea. I just decided to ignore those. I suppose I could try to build and
install fakeka if people seem to want it.
fakeka comes with the MIT Kerberos code now and Heimdal already has afs
stuff, so I don't think there's a need.
fakeka isn't built by default
Hi Kevin!!
Kevin Coffman wrote:
Yea. I just decided to ignore those. I suppose I could try to build and
install fakeka if people seem to want it.
fakeka comes with the MIT Kerberos code now and Heimdal already has afs
stuff, so I don't think there's a need.
fakeka isn't
On 9/23/05, Derek Atkins [EMAIL PROTECTED] wrote:
Quoting Christopher Allen Wing [EMAIL PROTECTED]: I included afs2k5db and fakeka, so that people could test out a server with less effort. (I put them in a separate
'openafs-server-krb5' package, though).Yea.I just decided to ignore those.I
I would suggest you do the same thing. The only annoying thing about the
OpenAFS aklog is that it seems to use 2b always; so if you are running
servers that don't support it then it gives you bad tokens unless you
explicitly specify -524.
I had a conversation about this with the other Derrick.
Ah. Ummm that's probably there because we had a dependency on linking
all Kerberos programs with -lresolv because we used the DNS code before it
made it into the mainline MIT tree. But since various bits of the kit
are making it into other packages, I've stopped caring about making the
Quoting Christopher Allen Wing [EMAIL PROTECTED]:
Yes, that's what I did to get afs-krb5 building. I eventually figured
out that Ken must have put it there to deal with old versions of
Kerberos, etc.
This is the patch I put in my openafs RPMs:
There are also a number of other patches to afs-krb5 I've accumulated in:
I've grabbed some that I consider relevant. I didn't grab all of them. I
tried
to ignore the UMich-specific stuff, and as I don't build/install afs2k5db I
just ignored that set completely.
Sure. Most are build fixes
Quoting Christopher Allen Wing [EMAIL PROTECTED]:
There are also a number of other patches to afs-krb5 I've accumulated in:
I've grabbed some that I consider relevant. I didn't grab all of
them. I tried
to ignore the UMich-specific stuff, and as I don't build/install afs2k5db I
just
Derek:
I didn't realize you had put packages up already. (I didn't bother to go
looking, I only checked out what was linked from the website)
I see you are also supporting Linux 2.4. I didn't bother to put in the
work since I only cared about deploying RHEL 4.
Solaris I'll believe. I'm
Quoting Christopher Allen Wing [EMAIL PROTECTED]:
I see you are also supporting Linux 2.4. I didn't bother to put in
the work since I only cared about deploying RHEL 4.
Yea, I'm trying to support fedora-1,3,4 and RHEL-3,4.
Hmm. I ended up rebuilding all the RPMs from the openafs site in the
Derek:
Hmm. I ended up rebuilding all the RPMs from the openafs site in the past
year because there were no x86_64 packages.
That's because I have no x86_64 hardware, and vmware doesn't emulate x86_64.
We need to start a collection and get you some money and/or x86_64
hardware. Seriously,
Quoting Christopher Allen Wing [EMAIL PROTECTED]:
We need to start a collection and get you some money and/or x86_64
hardware. Seriously, you are suffering :)
Heh.. I also need the space.. Seriously, I really wish there were a
VMware-like solution for x86_64. Much easier than having
I'm trying to compile openafs 1.4.0rc4 from the SRPM's. I am trying this on both RHEL AS 3 and RHEL AS 4.Openafs itself seems to compile OK but when the rpmbuild runs the configure script for afs-krb5 it gets the following error:make[1]: Leaving directory `/usr/src/redhat/BUILD/openafs-1.4.0-rc4'+
Quoting Kurt Seiffert [EMAIL PROTECTED]:
I'm trying to compile openafs 1.4.0rc4 from the SRPM's. I am trying
this on both RHEL AS 3 and RHEL AS 4.
both of these should work just fine. Although I believe I only used
WS, not AS.
Is there really a big difference between them?
Openafs itself
I was going to try to avoiding the check this morning.I do have the glibc-devel package installed on both. I'm not sure I understand everything in the test. Is there another quick way to test if res_search is available? My C programming is very rusty.Thanks.-KASP.S. Sorry about any duplicates on
Well, you could actually check the config.log in the afs-krb5 subdirectory and
see what's actually failing. That might give you some clue. On my RHEL3
system it finds res_search in -lresolv.
I do have access to a patch that removes res_search... I'll probably
just apply
that to the next
I already looked there. It wasn't very helpful to me. It just claimed an undefined reference to res_search. Which tends to tell me that it can't find the function can't be found in the library. One thing that bothers me is that the function declaration in the test C program, doesn't seem to match
Kurt Seiffert [EMAIL PROTECTED] writes:
[snip]
I tried bypassing the res_search check. ./configure ran successfully by hand
then but then the make blew up with the following:
gcc -c -g -O2 -I/usr/src/redhat/BUILD/openafs-1.4.0-rc4/afs-krb5/src/..
/../amd64_linux26/dest//include
Kurt Seiffert [EMAIL PROTECTED] writes:
I'm trying to compile openafs 1.4.0rc4 from the SRPM's. I am trying
this on both RHEL AS 3 and RHEL AS 4.
Openafs itself seems to compile OK but when the rpmbuild runs the
configure script for afs-krb5 it gets the following error:
checking for
Hi Derek,
I also get the res_search error while attempting to rebuild the source rpm,
this is again on the amd64 (x86_64) platform running RHEL 3. I've been
putting ugly, evil kludges into the spec file to make it look for
__res_search rather than res_search and then building from the spec.
Lester Barrows [EMAIL PROTECTED] writes:
Hi Derek,
I also get the res_search error while attempting to rebuild the source rpm,
this is again on the amd64 (x86_64) platform running RHEL 3. I've been
putting ugly, evil kludges into the spec file to make it look for
__res_search rather
Russ,
Russ Allbery [EMAIL PROTECTED] writes:
The slightly more robust cheat is to change anything like:
AC_SEARCH_LIBS([res_search], [resolv])
in configure.in or wherever to:
AC_SEARCH_LIBS([res_search], [resolv], ,
[AC_SEARCH_LIBS([__res_search], [resolv])])
I could do
I could do this.. But.. Is there any reason we need to do this at
all? Where does the code even _use_ res_search? Maybe KenH can pipe
up here about why he's searching for res_search in the configure
script? Is there some API that's needed on some platforms that's
shipped with res_search?
Quoting Ken Hornstein [EMAIL PROTECTED]:
I could do this.. But.. Is there any reason we need to do this at
all? Where does the code even _use_ res_search? Maybe KenH can pipe
up here about why he's searching for res_search in the configure
script? Is there some API that's needed on some
U ... what? I'm sorry, I wasn't paying attention to this discussion.
I don't recall ever adding anything to any OpenAFS configure.in script
that checks for res_search.
No, not openafs.. afs-krb5
Ah. Ummm that's probably there because we had a dependency on linking
all Kerberos
Hi Derek,
On Thursday 22 September 2005 12:21 pm, Derek Atkins wrote:
Oh, amd64! I don't recall that being stated before! That's the
issue. GLibc on amd64 doesn't export res_search in the same way as
x86. Honestly, I think we can probably just remove the res_search
checks, we really don't
Ken Hornstein [EMAIL PROTECTED] writes:
U ... what? I'm sorry, I wasn't paying attention to this discussion.
I don't recall ever adding anything to any OpenAFS configure.in script
that checks for res_search.
No, not openafs.. afs-krb5
Ah. Ummm that's probably there because we
Lester Barrows [EMAIL PROTECTED] writes:
Note that I edited the spec file, but that was just a few sed lines that
modify res_search in a few files and my attempt to disable krb5 to see if the
issue would go away. I can send it to you directly if you want to see what
mess I may have made of
Hi Derek,
You're absolutely right, not sure how the UTS_RELEASE became different from
the version of the kernel. I'll have to talk with the guy who installed this.
Thanks for the information! I rebuilt with the spec again, now I'm getting
this error though:
RPM build errors:
File not
Quoting Lester Barrows [EMAIL PROTECTED]:
Hi Derek,
You're absolutely right, not sure how the UTS_RELEASE became different from
the version of the kernel. I'll have to talk with the guy who installed this.
Thanks for the information!
NP. I /knew/ THAT code worked... Once I saw the output
Kurt Seiffert [EMAIL PROTECTED] writes:
I tried bypassing the res_search check. ./configure ran successfully by hand
then but then the make blew up with the following:
Okay, I've got changes now in my sources. This will be fixed in
the next package release.
Thanks for reporting it.
-derek
32 matches
Mail list logo
