Re: "make buildworld" failures with NO_KERBEROS=
Steve Kargl wrote: > On Fri, Jan 18, 2013 at 08:54:03PM +0100, Fabian Keil wrote: > > Recently "make buildworld" started failing for me: > > > > 8< > > ===> include/xlocale (installincludes) > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 _ctype.h > > _inttypes.h _langinfo.h _locale.h _monetary.h _stdio.h _stdlib.h _string.h > > _time.h _wchar.h /usr/obj/usr/src/tmp/usr/include/xlocale > > ===> kerberos5 (includes) > > set -e; cd /usr/src/kerberos5; /usr/obj/usr/src/make.amd64/make > > buildincludes; /usr/obj/usr/src/make.amd64/make installincludes > > ===> kerberos5/doc (buildincludes) > > ===> kerberos5/lib (buildincludes) > > ===> kerberos5/lib/libasn1 (buildincludes) > > compile_et > > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/asn1_err.et > > compile_et: No such file or directory > > *** [asn1_err.h] Error code 1 > > > > See the thread started here: > http://lists.freebsd.org/pipermail/freebsd-current/2013-January/039083.html Thanks. Fabian signature.asc Description: PGP signature
Re: "make buildworld" failures with NO_KERBEROS=
On Fri, Jan 18, 2013 at 08:54:03PM +0100, Fabian Keil wrote: > Recently "make buildworld" started failing for me: > > 8< > ===> include/xlocale (installincludes) > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 _ctype.h _inttypes.h > _langinfo.h _locale.h _monetary.h _stdio.h _stdlib.h _string.h _time.h > _wchar.h /usr/obj/usr/src/tmp/usr/include/xlocale > ===> kerberos5 (includes) > set -e; cd /usr/src/kerberos5; /usr/obj/usr/src/make.amd64/make > buildincludes; /usr/obj/usr/src/make.amd64/make installincludes > ===> kerberos5/doc (buildincludes) > ===> kerberos5/lib (buildincludes) > ===> kerberos5/lib/libasn1 (buildincludes) > compile_et > /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/asn1_err.et > compile_et: No such file or directory > *** [asn1_err.h] Error code 1 > See the thread started here: http://lists.freebsd.org/pipermail/freebsd-current/2013-January/039083.html AFAICT, it is an ordering issue. usr.bin/compile_et needs to be a bootstrap tool, but it depends on some bits from kerberos5 and building kerberos5 needs compile_et. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
"make buildworld" failures with NO_KERBEROS=
Recently "make buildworld" started failing for me: 8< ===> include/xlocale (installincludes) sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 _ctype.h _inttypes.h _langinfo.h _locale.h _monetary.h _stdio.h _stdlib.h _string.h _time.h _wchar.h /usr/obj/usr/src/tmp/usr/include/xlocale ===> kerberos5 (includes) set -e; cd /usr/src/kerberos5; /usr/obj/usr/src/make.amd64/make buildincludes; /usr/obj/usr/src/make.amd64/make installincludes ===> kerberos5/doc (buildincludes) ===> kerberos5/lib (buildincludes) ===> kerberos5/lib/libasn1 (buildincludes) compile_et /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/asn1_err.et compile_et: No such file or directory *** [asn1_err.h] Error code 1 Stop in /usr/src/kerberos5/lib/libasn1. *** [buildincludes] Error code 1 Stop in /usr/src/kerberos5/lib. *** [buildincludes] Error code 1 Stop in /usr/src/kerberos5. *** [includes] Error code 1 Stop in /usr/src/kerberos5. *** [kerberos5.includes__D] Error code 1 Stop in /usr/src. *** [_includes] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. 8< I was still using the recently de-supported NO_KERBEROS= and changing it to WITHOUT_KERBEROS= got it working again. I'm still wondering if this is the expected behaviour, though. Shouldn't buildworld create a usable compile_et instead of relying on compile_et's existence in /usr/bin? Fabian signature.asc Description: PGP signature
Re: Buildworld failures
On Sat, 4 Mar 2000, Jeff Palmer wrote: > I have cvsupped and tried to build world mutiple times over the past 3 > days, each time I get the same error. I have been following the mailing > lists and don't see any other complaints.. So I'm sure the trouble is > with my machine... Are you building with NO_OPENSSL? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld failures
Are you building with -DNOSHARE? That is the only way I can think of off the top of my head. Jim Bloom [EMAIL PROTECTED] Jeff Palmer wrote: > > Hi all, > > I have cvsupped and tried to build world mutiple times over the past 3 > days, each time I get the same error. I have been following the mailing > lists and don't see any other complaints.. So I'm sure the trouble is > with my machine... > > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to > `ERR_load_RSAREF_strings' > /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to > `RSA_PKCS1_RSAref' > *** Error code 1 > Stop in /usr/src/usr.sbin/ppp. > *** Error code 1 > > anyone know what may be causing this, and what I may be able to do, to > correct? > > Please CC: any replies to: > [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Buildworld failures
Hi all, I have cvsupped and tried to build world mutiple times over the past 3 days, each time I get the same error. I have been following the mailing lists and don't see any other complaints.. So I'm sure the trouble is with my machine... /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' /usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to `RSA_PKCS1_RSAref' *** Error code 1 Stop in /usr/src/usr.sbin/ppp. *** Error code 1 anyone know what may be causing this, and what I may be able to do, to correct? Please CC: any replies to: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libpam related buildworld failures
On Wed, 3 Feb 1999, John Polstra wrote: > That's what I meant by: > > If you instead meant things like support for RADIUS accounting, > that's just waiting for somebody to come along and implement the > necessary support in libradius and the corresponding PAM module. No. I don't want/need radious support. kdm and samba only do password authentication AFAIK, why they don't use the "auth" method (or whatever) I don't know. They work without Radius and without Pam.. but that doesn't fix the underlying problem > I'm going to work now. Gotta keep food on the table. Bye! :-) Have fun! ;) - alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: libpam related buildworld failures
Alex Zepeda wrote: > No I meant service as in authentication types or tasks whatever ya call > it. From the man page: Well, "service type" is a specific term in PAM that refers to things like "login", "ftp", "ppp", and so forth. >PAM separates the tasks of authentication into four inde- >pendent management groups: account management; authentica- >tion management; password management; and session manage- >ment. (We highlight the abbreviations used for these >groups in the configuration file.) > > > authentication works.. but everything else gives unresolved (or defined) > symbols... so kdm, xdm, and samba don't work with pam on FreeBSD (well > those are the ones I've tried). That's what I meant by: If you instead meant things like support for RADIUS accounting, that's just waiting for somebody to come along and implement the necessary support in libradius and the corresponding PAM module. I'm going to work now. Gotta keep food on the table. Bye! :-) John --- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: libpam related buildworld failures
No I meant service as in authentication types or tasks whatever ya call it. From the man page: PAM separates the tasks of authentication into four inde- pendent management groups: account management; authentica- tion management; password management; and session manage- ment. (We highlight the abbreviations used for these groups in the configuration file.) authentication works.. but everything else gives unresolved (or defined) symbols... so kdm, xdm, and samba don't work with pam on FreeBSD (well those are the ones I've tried). - alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: libpam related buildworld failures
Alex Zepeda wrote: > > Well I should have rephrased that. I was curious if anyone knew about it > or was working on it. What exactly needs to be done here (I know next to > nothing about pam)? Well, if by "service types" you meant login, ftp, telnet, etc., then what needs to be done is to convert ftpd, telnetd, etc. to use PAM instead of doing their own authentication. For ftpd that will require a few relatively minor PAM module fixes having to do with the fact that FTP as viewed from the server is sort of an event-driven machine rather than an interactive conversation. That's what my near-term focus is on. If you instead meant things like support for RADIUS accounting, that's just waiting for somebody to come along and implement the necessary support in libradius and the corresponding PAM module. John --- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: libpam related buildworld failures
On Wed, 3 Feb 1999, John Polstra wrote: > Alex Zepeda wrote: > > Speaking of pam, when will it be fixed to support all the various service > > types? Or is that a do it yourself project? > > As you know, questions of the form "when will X happen" rarely get > useful answers around here. So here's my useless answer: "When it's > finished." :-) I'm working on it as fast as my available time permits. Well I should have rephrased that. I was curious if anyone knew about it or was working on it. What exactly needs to be done here (I know next to nothing about pam)? - alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: libpam related buildworld failures
Alex Zepeda wrote: > Speaking of pam, when will it be fixed to support all the various service > types? Or is that a do it yourself project? As you know, questions of the form "when will X happen" rarely get useful answers around here. So here's my useless answer: "When it's finished." :-) I'm working on it as fast as my available time permits. John --- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: libpam related buildworld failures
Speaking of pam, when will it be fixed to support all the various service types? Or is that a do it yourself project? - alex To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
libpam related buildworld failures
There have been some reports of builds failing in libpam. With help from Jon Hamilton, I've narrowed down the causes. There are at least two different failure modes, but the solution is the same in either case. * Don't define OBJLINK. It is badly broken, and a libpam build failure happens to be the first symptom you're likely to see. * Don't define NOCLEAN. * Scan your entire source tree and make sure there are no symbolic links named "obj" there. Remove any that you find. * Scan your source tree under "/usr/src/lib/libpam" and make sure there are no symbolic links at all. Remove any that you find. * Scan your source tree under "/usr/src/lib/libpam" and make sure there are no files with names matching "*.[oa]" or "*.?o" there. Remove any that you find. Don't assume that a "make clean" or "make cleandir" will remove the files above. Check manually using "find". Once your source tree is cleaned up, if you avoid using OBJLINK, it will stay clean. Note, these problems have nothing to do with libpam. It's just the thing that's getting clobbered by polluted source trees resulting from unrelated breakage. John --- John Polstra j...@polstra.com John D. Polstra & Co., Inc.Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
