Re: Resolution (Was: Re: The future of perl on FreeBSD)
Richard Arends wrote: On Thu, 9 May 2002, Mark Murray wrote: Can somebody, or maybe you, make a list off the perl script in the base OS, that need to be rewritten?? Of course! :). Done, sent to current@ Perfect... What is preffered: C, Shell ??? Uh, csh. Preferrably with tcsh extensions, so it won't run anywhere else. In a pinch, I guess you could use bash. cackles maniacally, and ducks -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
I need 96 bytes less of boot2, anyone want to hack?
When building /sys/boot on i386 with Gcc 3.1, one gets -96 bytes
available. Anyone want to install the gcc31 port, build /sys/boot with
make CC=gcc31 and try to hack out 96 bytes?
You will need this diff also.
Index: boot2/Makefile
===
RCS file: /home/ncvs/src/sys/boot/i386/boot2/Makefile,v
retrieving revision 1.22
diff -u -r1.22 Makefile
--- boot2/Makefile 31 Jul 2001 19:50:09 - 1.22
+++ boot2/Makefile 8 May 2002 23:30:16 -
@@ -27,10 +27,10 @@
ORG1= 0x7c00
ORG2= 0x1000
-CFLAGS=-elf -I${.CURDIR}/../btx/lib -I. \
- -Os -fno-builtin -fforce-addr -fdata-sections \
- -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd \
- -mpreferred-stack-boundary=2 \
+CFLAGS=-elf -ffreestanding -Os -fno-builtin -fforce-addr -fdata-sections \
+ -fno-align-functions -fno-align-jumps -fno-align-loops -fno-align-labels \
+ -mrtd -mpreferred-stack-boundary=2 \
+ -I${.CURDIR}/../btx/lib -I. \
-Wall -Waggregate-return -Wbad-function-cast -Wcast-align \
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs \
-Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Resolution (Was: Re: The future of perl on FreeBSD)
On Thu, 9 May 2002, Terry Lambert wrote: Uh, csh. Preferrably with tcsh extensions, so it won't run anywhere else. In a pinch, I guess you could use bash. As far i can see, (almost?) everything is already moved from perl to something else. Asked it, went away for a few hours and all the work is done :-) Greetings, Richard. An OS is like swiss cheese, the bigger it is, the more holes you get! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The future of perl on FreeBSD
On Thu, May 09, 2002 at 07:16:31PM +0200, Miguel Mendez wrote:
Ports should avoid messing with stuff outside of ${PREFIX} if they can
help it. Existing systems will already have a /usr/bin/perl on them
unless the user goes and removes it. People writing or executing scripts for
new systems can easily figure out something is wrong when they get:
Now that I think of it, you are absolutely right, John. Just let's make
a big big banner saying Perl is no longer in base so everybody notices
Ok, then. What is so wrong with /usr/bin/perl being /usr/bin/env perl,
or DES's wrapper?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RE: I need 96 bytes less of boot2, anyone want to hack?
On 09-May-2002 David O'Brien wrote:
When building /sys/boot on i386 with Gcc 3.1, one gets -96 bytes
available. Anyone want to install the gcc31 port, build /sys/boot with
make CC=gcc31 and try to hack out 96 bytes?
Argh! Can't we go one update of gcc w/o them adding some weird optimizations
that bloat the code. :( *sigh* I'll try to look into this.
You will need this diff also.
Index: boot2/Makefile
===
RCS file: /home/ncvs/src/sys/boot/i386/boot2/Makefile,v
retrieving revision 1.22
diff -u -r1.22 Makefile
--- boot2/Makefile31 Jul 2001 19:50:09 - 1.22
+++ boot2/Makefile8 May 2002 23:30:16 -
@@ -27,10 +27,10 @@
ORG1=0x7c00
ORG2=0x1000
-CFLAGS= -elf -I${.CURDIR}/../btx/lib -I. \
- -Os -fno-builtin -fforce-addr -fdata-sections \
- -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd \
- -mpreferred-stack-boundary=2 \
+CFLAGS= -elf -ffreestanding -Os -fno-builtin -fforce-addr
-fdata-sections \
+ -fno-align-functions -fno-align-jumps -fno-align-loops
-fno-align-labels \
+ -mrtd -mpreferred-stack-boundary=2 \
+ -I${.CURDIR}/../btx/lib -I. \
-Wall -Waggregate-return -Wbad-function-cast -Wcast-align \
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs \
-Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Resolution (Was: Re: The future of perl on FreeBSD)
[bogus From: address, because people cannot be bothered to respect Reply-To:] On Thu, May 09, 2002 at 09:32:10AM -0700, Gordon Tetlow wrote: Why?? If someone wants to use perl in building a port, let them. Add a BUILD_DEPENDS. Seems like an awful amount of installation if all you are going to be doing with it is something that can be easily acheived by sed (which is probably the biggest case). Please don't be telling a maintainer how to do his job. If you want to push a direction of a port, become its maintainer. (I dare say even 90% of Perl haters will have it installed anyway, so using is not such a big deal) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I need 96 bytes less of boot2, anyone want to hack?
I had to recover about this amount, before.
The way I ended up doing it was to hack all the strings shorter.
Boots were ugly, but they worked. 8-(.
-- Terry
David O'Brien wrote:
When building /sys/boot on i386 with Gcc 3.1, one gets -96 bytes
available. Anyone want to install the gcc31 port, build /sys/boot with
make CC=gcc31 and try to hack out 96 bytes?
You will need this diff also.
Index: boot2/Makefile
===
RCS file: /home/ncvs/src/sys/boot/i386/boot2/Makefile,v
retrieving revision 1.22
diff -u -r1.22 Makefile
--- boot2/Makefile 31 Jul 2001 19:50:09 - 1.22
+++ boot2/Makefile 8 May 2002 23:30:16 -
@@ -27,10 +27,10 @@
ORG1= 0x7c00
ORG2= 0x1000
-CFLAGS=-elf -I${.CURDIR}/../btx/lib -I. \
- -Os -fno-builtin -fforce-addr -fdata-sections \
- -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd \
- -mpreferred-stack-boundary=2 \
+CFLAGS=-elf -ffreestanding -Os -fno-builtin -fforce-addr -fdata-sections \
+ -fno-align-functions -fno-align-jumps -fno-align-loops -fno-align-labels \
+ -mrtd -mpreferred-stack-boundary=2 \
+ -I${.CURDIR}/../btx/lib -I. \
-Wall -Waggregate-return -Wbad-function-cast -Wcast-align \
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs \
-Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings
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
Re: The future of perl on FreeBSD
On Thu, May 09, 2002 at 12:55:42PM -0400, John Baldwin wrote:
Hi,
Ports should avoid messing with stuff outside of ${PREFIX} if they can
help it. Existing systems will already have a /usr/bin/perl on them
unless the user goes and removes it. People writing or executing scripts for
new systems can easily figure out something is wrong when they get:
Now that I think of it, you are absolutely right, John. Just let's make
a big big banner saying Perl is no longer in base so everybody notices
:)
Cheers,
--
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
FreeBSD - The power to serve!
msg38107/pgp0.pgp
Description: PGP signature
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /tmp/des/obj/alpha/.amd_mnt/freefall/host/d/home/des/tinderbox/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === usr.sbin/rpc.umntall ... /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.umntall/rpc.umntall.c: In function `do_umntall': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.umntall/rpc.umntall.c:185: warning: passing arg 3 of pointer to function from incompatible pointer type /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.umntall/rpc.umntall.c:185: warning: passing arg 5 of pointer to function from incompatible pointer type /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.umntall/rpc.umntall.c: In function `do_umount': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.umntall/rpc.umntall.c:211: warning: passing arg 3 of pointer to function from incompatible pointer type /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.umntall/rpc.umntall.c:211: warning: passing arg 5 of pointer to function from incompatible pointer type === usr.sbin/rpc.yppasswdd cc1: warnings being treated as errors /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.yppasswdd/yppasswdd_server.c: In function `update_inplace': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.yppasswdd/yppasswdd_server.c:366: warning: field width is not type int (arg 5) *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin/rpc.yppasswdd. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.sbin. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Perl scripts that need rewiting - Any volunteers?
On 09-May-2002 (15:38:45/GMT) Mark Murray wrote: I tryed this one. I'm not a committer, just a volunteer :-) You're on! Please put appropriate (c) on this (Preferably 2-clause BSD license) and I'll commit it for you :-) Ahemm, I'm not sure to have done correct job. Please review last version of this script from my site: ftp://castle.torrini.org/pub/FreeBSD/spkrtest-current and modify if I miss or don't understand something ;) Thanks. Riccardo. PS: I think that man page (/usr/src/usr.sbin/spkrtest/spkrtest.8) should be changed to remove perl(1): # diff -u2 spkrtest.8.orig spkrtest.8 --- spkrtest.8.orig Fri Jul 13 17:36:02 2001 +++ spkrtest.8 Thu May 9 20:43:40 2002 @@ -40,5 +40,4 @@ .Sh SEE ALSO .Xr dialog 1 , -.Xr perl 1 , .Xr spkr 4 .Sh HISTORY or to include sh(1): # diff -u2 spkrtest.8.orig spkrtest.8 --- spkrtest.8.orig Fri Jul 13 17:36:02 2001 +++ spkrtest.8 Thu May 9 20:58:46 2002 @@ -40,5 +40,5 @@ .Sh SEE ALSO .Xr dialog 1 , -.Xr perl 1 , +.Xr sh 1 , .Xr spkr 4 .Sh HISTORY To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Perl scripts that need rewiting - Any volunteers?
On 09-May-2002 (15:38:45/GMT) Mark Murray wrote: I tryed this one. I'm not a committer, just a volunteer :-) You're on! Please put appropriate (c) on this (Preferably 2-clause BSD license) and I'll commit it for you :-) Ahemm, I'm not sure to have done correct job. Please review last version of this script from my site: ftp://castle.torrini.org/pub/FreeBSD/spkrtest-current and modify if I miss or don't understand something ;) Thanks. Looks fine to me! Thanks! Commit will come later... M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Perl scripts that need rewriting - Progress!
Hi The response to the perl-script rewriting project has been very hearteningly _fantastic_! Here is the list as it stands. The gaps are fairly obvious (and probably mostly not critical in the short term): /usr/bin/afmtodit /usr/bin/catman John Rochester [EMAIL PROTECTED] - re /usr/bin/makewhatis John Rochester [EMAIL PROTECTED] - re /usr/bin/mmroff /usr/bin/sockstat des - re /usr/bin/whereissheldonh - re /usr/sbin/adduser Mike Makonnen [EMAIL PROTECTED] - re /usr/sbin/kbdmapJonathan Belson [EMAIL PROTECTED] - re /usr/sbin/pkg_updatepaul - del - done /usr/sbin/pkg_version Jeremy Lea [EMAIL PROTECTED] - re /usr/sbin/rmuserMike Makonnen [EMAIL PROTECTED] - re /usr/sbin/scriptdump /usr/sbin/spkrtest Riccardo Torrini [EMAIL PROTECTED] - re - ready /usr/sbin/vidfont Jonathan Belson [EMAIL PROTECTED] - re Key - re == to be rewritten del == to be deleted ready == work done, just waiting for commit. done == completed M -- o Mark Murray \_ O.\_Warning: this .sig is umop ap!sdn #text/plain; name=cv.doc [Mark Murray CV Plain Text] cv.doc #application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The future of perl on FreeBSD
David O'Brien [EMAIL PROTECTED] writes: Ok, then. What is so wrong with /usr/bin/perl being /usr/bin/env perl, or DES's wrapper? People just need something to be righteously wroth about. Moving perl out of the base is no longer open to debate, so they've found another bikeshed to argue about. Please stop this thread. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
world broken in yppasswd_svc.c
yppasswd_svc.c: In function 'yppasswdprog_1': yppasswd_svc.c:100: warning passing arg 1 of '_msgout' discards qualifiers from pointer target types ***Error code 1 1 error ***Error code 2 1 error ***Error code 2 1 error ***Error code 2 1 error ***Error code 2 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld broken in usr.sbin/rpc.yppasswdd
Pawel Worach [EMAIL PROTECTED] writes:
Any idea?
rpcgen needs to be a bootstrap tool, but isn't. This has been broken
for a long time, just not visibly. Try the attached patch.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
Index: Makefile.inc1
===
RCS file: /home/ncvs/src/Makefile.inc1,v
retrieving revision 1.268
diff -u -r1.268 Makefile.inc1
--- Makefile.inc1 8 May 2002 20:35:12 - 1.268
+++ Makefile.inc1 9 May 2002 20:45:43 -
@@ -583,7 +583,7 @@
bootstrap-tools:
.for _tool in ${_strfile} usr.bin/yacc usr.bin/colldef \
-usr.bin/xargs usr.bin/xinstall \
+usr.bin/rpcgen usr.bin/xargs usr.bin/xinstall \
usr.sbin/config usr.sbin/kbdcontrol \
gnu/usr.bin/gperf gnu/usr.bin/groff gnu/usr.bin/texinfo
cd ${.CURDIR}/${_tool}; \
Re: does the order of .a files matter?
On Wednesday 08 May 2002 09:52 pm, Terry Lambert wrote: = Mikhail Teterin wrote: [...] = The most frustrating thing is, the number of such symbols varies = greatly with the order, in which I list the libraries on the command = line. Is not the linker supposed to make several runs over the given = libraries if needed? = = No. It doesn't make several runs. It only does that for single = object files. Is there a reason for it, or this just a not-yet-implemented feature? It certainly seems like the latter -- why make the user jump through all the sorting/reordering hoops? = You might also want to consider using -Lpath -llibrary, instead = of trying to link .a's directly. What would this do? Thanks! -mi P.S. Yes, packing all object files into a single giant .a helped... -- Êàê, Âû ðàçâå áåç øïàãè ïðèøëè? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Perl scripts that need rewiting - Any volunteers?
Mark Murray wrote: [bogus From: address, because people cannot be bothered to respect Reply-To :] On Thu, May 09, 2002 at 10:57:00AM +0100, Mark Murray wrote: It would be acceptable to rewrite in C (C++?) NO! for rewriting in C++. If you do, you'll soon see the consequences. (and that is all I am going to elude to at this time) Need info here :-). Has this to do with GCC 3.x? Yes. The problem is libstdc++-v3. (And if so, are we in trouble with groff?) Partly. groff isn't a big libstdc++ user. It is mostly a C-with-classes and almost exclusively a libc user. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: does the order of .a files matter?
Mikhail Teterin wrote: = The most frustrating thing is, the number of such symbols varies = greatly with the order, in which I list the libraries on the command = line. Is not the linker supposed to make several runs over the given = libraries if needed? = = No. It doesn't make several runs. It only does that for single = object files. Is there a reason for it, or this just a not-yet-implemented feature? It certainly seems like the latter -- why make the user jump through all the sorting/reordering hoops? Generally, this won't be necessary for properly organized code. The code in question is organized by software layering, right, so all you have to do is link the libraries in order? = You might also want to consider using -Lpath -llibrary, instead = of trying to link .a's directly. What would this do? Make it all go through the library linking code, instead of the single object archive linking code. a .a file treated as an object is not the same as a library. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The future of perl on FreeBSD
On Thu, May 09, 2002 at 05:31:49PM +0200, Sheldon Hearn wrote:
On Thu, 09 May 2002 08:24:57 MST, Joseph Scott wrote:
This may sound like an extremely silly little idea, but is there
any reason why we can't just replace /usr/bin/perl with a shell script
that prints out something like :
Perl is no longer comes with the base install of FreeBSD, please install
it from your ports collection, in /usr/ports/lang/perl5.
We don't want the port to overwrite a script that exists in userland,
and we don't want installworld blowing away (or, even worse, following)
the port's symlink.
Symlink or redirector, but please not this. :-)
Shouldn't ports *not* touch anything outside of ${PREFIX}? I, for
one, can't stand when ports do that (except /etc/shells -- that's
different).
Seems that neither symlink nor redirector is neccesary; portable
perl shebangs use #!/usr/bin/env perl to search $PATH for it, and
if the local sysadmin wants they can make a symlink.
--
Jordan DeLong
[EMAIL PROTECTED]
msg38119/pgp0.pgp
Description: PGP signature
Re: The future of perl on FreeBSD
Jordan DeLong [EMAIL PROTECTED] writes: Seems that neither symlink nor redirector is neccesary; portable perl shebangs use #!/usr/bin/env perl to search $PATH for it, and if the local sysadmin wants they can make a symlink. Most Perl scripts use '#!/usr/bin/perl'; also, using a redirector has the very nice side effect of clobbering the old Perl binary. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The future of perl on FreeBSD
At 6:29 PM -0500 5/9/02, Jordan DeLong wrote:
Symlink or redirector, but please not this. :-)
Shouldn't ports *not* touch anything outside of ${PREFIX}?
I, for one, can't stand when ports do that
(except /etc/shells -- that's different).
I agree. That's why a redirector makes more sense, because
the redirector can be part of the base-system, and the port
can be installed in /usr/local.
Seems that neither symlink nor redirector is neccesary;
portable perl shebangs use #!/usr/bin/env perl to search
$PATH for it, and if the local sysadmin wants they can
make a symlink.
Many many perl scripts already exist which do not do this.
Yes, we now know that it would be more portable to write
a script that way, but that doesn't magically change all
the scripts which are already written and which are very
used to assuming that perl is at /usr/bin/perl.
Also, the /usr/bin/env approach means that scripts are
now subject to the setting of $PATH, and that is not
necessarily a good thing. Remember that the person
running the script is not necessarily the person who
wrote it, and is not necessarily aware that it even
is a perl script, or that PATH is important when
running that script. (PATH would not be important
for a script which is using /usr/bin/perl)
--
Garance Alistair Drosehn= [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Instituteor [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
HEADS UP - gcc-3.1 in progress!
David O'Brien is in the process of committing gcc-3.1. If you are not prepared to do your own fixing, now would be a good time to avoid -current. It is a big task and will take a while to finish, so please be patient! Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: HEADS UP - gcc-3.1 in progress!
On 10-May-2002 Peter Wemm wrote: David O'Brien is in the process of committing gcc-3.1. If you are not prepared to do your own fixing, now would be a good time to avoid -current. It is a big task and will take a while to finish, so please be patient! Cheers, -Peter YAY!! *and the crowd goes wild* So how many cases of beer does O'Brien get at Usenix now? :) -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /tmp/des/obj/i386/d/home/des/tinderbox/src/i386/usr/include -- stage 4: building libraries -- === cccp ... /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:77: warning: implicit declaration of function `__va_size' /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:77: syntax error before `const' /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:77: syntax error before `const' /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:80: syntax error before `const' /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:80: syntax error before `const' /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:83: syntax error before `char' /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:83: syntax error before `char' *** Error code 1 Stop in /d/home/des/tinderbox/src/kerberos5/lib/libkrb5. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: i386 tinderbox failure
On Thu, May 09, 2002 at 07:48:47PM -0700, Dag-Erling Smorgrav wrote: ... /d/home/des/tinderbox/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/acl.c:77: warning: implicit declaration of function `__va_size' fixed. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
