Date: Wed, 29 Sep 1999 16:54:44 -0400 (EDT) From: Jim.Pirzyk@disney.com To: FreeBSD-gnats-submit@freebsd.org Subject: bin/14040: amd has wrong uname data compile in it Message-ID: <199909292054.QAA83350@amigo.faf.fa.disney.com>
next in thread | raw e-mail | index | archive | help
>Number: 14040 >Category: bin >Synopsis: amd has wrong uname data compile in it >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Sep 29 14:10:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Jim Pirzyk >Release: FreeBSD 3.3-RELEASE i386 >Organization: >Environment: When upgrading to FreeBSD 3.3, I did a make world in /usr/src. When amd got compiled, it saw that I was currently running 3.2-RELEASE. It put that into the amd binary. When I rebooted, I was running 3.3-RELEASE. This means that amd had the wrong info. >Description: Amd had the OS version of the system it was compiled on, not the system that it is running on. >How-To-Repeat: Compile amd on one version of the OS and put it on another. >Fix: Have amd call the uname C library function at run time to set the $os and $osver variables. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909292054.QAA83350>