From owner-freebsd-bugs Thu Sep 30 9:30: 9 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B3B09159F9 for ; Thu, 30 Sep 1999 09:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA17763; Thu, 30 Sep 1999 09:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 30 Sep 1999 09:30:02 -0700 (PDT) Message-Id: <199909301630.JAA17763@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/14040: amd has wrong uname data compile in it Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/14040; it has been noted by GNATS. From: Sheldon Hearn To: Jim Pirzyk Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/14040: amd has wrong uname data compile in it Date: Thu, 30 Sep 1999 18:28:28 +0200 On Thu, 30 Sep 1999 12:05:43 -0400, Jim Pirzyk wrote: > I see, said the blind man. I cannot answer the question if it is > storing the osver at compile time because it may not be able to get it > at run time. Maybe it was before most systems had the uname C library > routine, so it had to be compiled in? Could be. I'll have a closer look at where (if at all) amd users osversion internally. :-) Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message