Bug 25793

Summary: Fw: misc/25249: cc compiler not work
Product: Base System Reporter: stado_slonov <stado_slonov>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 1.0-RELEASE   
Hardware: Any   
OS: Any   

Description stado_slonov 2001-03-14 07:20:02 UTC 
 ----- Original Message ----- 
 > ----------------
 > From: "Peter Avalos" <pavalos@theshell.com>
 > To: <freebsd-gnats-submit@FreeBSD.org>, <stado_slonov@mail.ru>
 > Cc:  
 > Subject: Re: misc/25249: cc compiler not work
 > Date: Wed, 28 Feb 2001 13:37:58 -0600
 > 
 >  Which version of socket.h do you have, and when did you last update your
 >  source tree?
 >  
 >  --Pete
 >  --------------
 > *      @(#)socket.h    8.4 (Berkeley) 2/21/94
 >  * $FreeBSD: src/sys/sys/socket.h,v 1.49 2001/02/17 03:49:24 bde Exp $
 >  */
 > -rw-r--r--  1 root  wheel  15621 17 oaa 06:49 /usr/src/sys/sys/socket.h
 > ---------------
 > the machine with FreeBSD 5.0 cur. rebooting every 12 hours :-( itself ...
 > -----
 > root@sys /usr/src/include# last
 > reboot           ~                         thu   8 mar 05:00
 > reboot           ~                         wed   5 mar 05:05
 > wtmp begins  thu   1 mar 12:35:19 2001
 > root@sys /usr/src/include#
 > -----
Comment 1 Poul-Henning Kamp freebsd_committer freebsd_triage 2001-04-04 08:38:57 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

over to bugs
Comment 2 Poul-Henning Kamp freebsd_committer freebsd_triage 2001-04-04 08:38:57 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

over to bugs
Comment 3 Poul-Henning Kamp freebsd_committer freebsd_triage 2001-04-04 08:38:57 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

over to bugs
Comment 4 Poul-Henning Kamp freebsd_committer freebsd_triage 2001-04-04 08:38:57 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

over to bugs
Comment 5 Jens Schweikhardt freebsd_committer freebsd_triage 2001-06-15 15:01:40 UTC 
State Changed
From-To: open->closed

Broken PR. Subject doesn't seem to match body, no usable 
information, repeated audit trails referencing unrelated 
PRs and probably a -current problem which should be discussed 
in the mailing list and not using a PR. If the originator or 
whoever thinks this is worth a PR, please resubmit the PR.