From owner-freebsd-hackers Mon Jul 19 0:55:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wenet.net (tibet-58.ppp.hooked.net [206.80.9.186]) by hub.freebsd.org (Postfix) with ESMTP id 56FAB1505A for ; Mon, 19 Jul 1999 00:55:18 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by wenet.net (8.9.3/8.9.1) with ESMTP id AAA04517; Mon, 19 Jul 1999 00:55:06 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 19 Jul 1999 00:55:05 -0700 (PDT) From: Alex Zepeda To: Per Lundberg Cc: hackers@FreeBSD.ORG Subject: Re: glibc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Jul 1999, Per Lundberg wrote: > You think so? Yes. > I experience a lot of this when I try to recompile stuff for FreeBSD > (most of it are due to lack of a real getopt routine). *sigh* It's quite easily argued that depending on a *NON STANDARD* getopt routine is a bug. AFAIK *ONLY* glibc has the long-getopt crap, and if that's the only thing you're running into, it should be easy enough to rip out the long getopt code, and add a few proper defines and have the standard libc coexist peacefully with the GNU getopt. > > c.) dependencies on bugs in glibc. > > What bugs have you found in glibc 2.1.1? Have you reported those to the > GNU folks? I personally haven't found any, but I've seen for instance, kcalc is riddled with ifdefs and warnings about floating point precision stuff and RH 5.something due to glibc bug(s). - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message