Terry, I have a high speed connection over here, so if its purely a 'typing' change sort of thing, if you want to tell me what needs to be done to fix these, I can make the changes and submit patches (I can't login to my FreeBSD account to make the commits myself ... my key went out of date *sigh*) ...
On Mon, 3 Jun 2002, Kris Kennaway wrote: > On Mon, Jun 03, 2002 at 04:54:32PM -0700, Terry Lambert wrote: > > Kris Kennaway wrote: > > > > But the error handling path of any program is not one of them; if > > > > you are optimizing something other than the success path, there is > > > > something fundamentally wrong with your program or problem statement. > > > > > > So how about you do more than the average person's part towards > > > reducing the amount of evil in the world, by fixing broken ports and > > > submitting patches. I can give you a list of the broken ports. > > > > I have a slow link. As long as the ports aren't the size of > > "Mozilla", I would be willing to use my slow link to hack some > > of them to not directly reference the error lists from libc. > > Thanks, that would be great. Here's the sys_nerr list so far: > > NeTraMet-4.3.log:../../src/bgp/integrat/readbgp.c:118: conflicting types for >`sys_nerr' > arm-aout-gcc295-2.95.3.log:strerror.c:465: conflicting types for `sys_nerr' > arm-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > avr-binutils-2.11.log:strerror.c:468: conflicting types for `sys_nerr' > bc-gcc-2.7.2p1.0.2.log:gcc.c:178: conflicting types for `sys_nerr' > bogosort-0.3.3.log:error.c:126: conflicting types for `sys_nerr' > cap-6.0.198.log:ablog.c:94: conflicting types for `sys_nerr' > coco-2.3.log:emacs.c:514: conflicting types for `sys_nerr' > cwish-3.52.log:header.c:121: conflicting types for `sys_nerr' > dlx-2.0.log:sim.c:2835: conflicting types for `sys_nerr' > dviselect-1.3.log:error.c:36: conflicting types for `sys_nerr' > egcs-1.1.2.log:strerror.c:465: conflicting types for `sys_nerr' > gcc-2.7.2.3.log:gcc.c:182: conflicting types for `sys_nerr' > gup-0.4.log:rfc822.h:247: conflicting types for `sys_nerr' > harvest-1.5.log:print.c:80: conflicting types for `sys_nerr' > i386-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > i960-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > ja-okphone-1.2.log:misc.c:34: conflicting types for `sys_nerr' > ko-hanemacs-19.34b.1.log:emacs.c:434: conflicting types for `sys_nerr' > >m3gdb-4.17.log:/tmp/a/ports/lang/m3gdb/work/m3gdb-4.17/src/contrib/binutils/libiberty/strerror.c:465: > conflicting types for `sys_nerr' > m6811-binutils-2.10.log:strerror.c:465: conflicting types for `sys_nerr' > m68k-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > mgetty-1.1.28.01.10.log:logfile.c:55: conflicting types for `sys_nerr' > mips-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > mipsel-linux-binutils-2.10.91.log:strerror.c:468: conflicting types for `sys_nerr' > objprelink-1.0_2.log:strerror.c:468: conflicting types for `sys_nerr' > pgcc-2.95.2.1.log:strerror.c:465: conflicting types for `sys_nerr' > powerpc-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > sdcc-2.1.9.log:cpplib.c:7451: conflicting types for `sys_nerr' > sdcc-2.1.9.log:cpplib.c:7451: conflicting types for `sys_nerr' > sh-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > sparc-rtems-binutils-2.11.2.log:../../binutils-2.11.2/libiberty/strerror.c:468: >conflicting types for `sys_nerr' > squid-2.4_9.log:util.c:79: conflicting types for `sys_nerr' > tintin-1.5.9.log:utils.c:60: conflicting types for `sys_nerr' > zh-tintin-1.5.9.log:utils.c:60: conflicting types for `sys_nerr' > > There are others hidden by dependencies that fail to build. > > > This is an exercise that's more about typing speed than thinking, > > anyway. > > For the most part, yeah. There are probably some tricky ones. For > example, some of the stdio breakage is difficult to fix. > > Kris > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
