From owner-freebsd-current Tue Nov 13 11:54: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailout05.sul.t-online.de (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id A77B137B405 for ; Tue, 13 Nov 2001 11:54:04 -0800 (PST) Received: from fwd07.sul.t-online.de by mailout05.sul.t-online.de with smtp id 163j33-0002FG-04; Tue, 13 Nov 2001 20:16:41 +0100 Received: from twoflower (320072111332-0001@[217.80.127.8]) by fwd07.sul.t-online.com with smtp id 163j2t-16t1d2C; Tue, 13 Nov 2001 20:16:31 +0100 From: Jan.Stocker@t-online.de (Jan Stocker) To: "freebsd-current@FreeBSD. ORG" Subject: struct thread Date: Tue, 13 Nov 2001 20:15:49 +0100 Message-ID: <004301c16c77$9a61e720$fe02010a@twoflower.liebende.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <20011113195619.A920@tara.freenix.org> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal X-Sender: 320072111332-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FYI: Ive posted an article to comp.emulators.ms-windows.wine about compiling errors for wine. This is caused by an redefinition of "struct thread". This is the state at present: From: kargls@home.com (Steven G. Kargl) Subject: Re: Compile errors with FreeBSD 5.0 Newsgroups: comp.emulators.ms-windows.wine In article , Ove Kaaven writes: > >> Jan Stocker wrote: >> > Hi, >> > the current version of FreeBSD (5.0) has a common header which defines >> > struct thread, so there will be an redefinition and nothing works. I >> > think you shall rename your stuff from thread.h to something like wine_thre >> > to get out of this trouble. > > I'd rather say that the problem is FreeBSD. System headers should not > pollute the namespace of applicatio. The glibc headers take great care to > avoid polluting the namespace, but FreeBSD is starting to look like it > thinks that it can define any common name, and if there's a collision > because of that carelessness, they tell all the apps to rename their > symbols, instead of fixing the OS. Can you elaborate? The application is pulling in the system header sys/proc.h where struct thread is defined. If an application purposely pulls in a system header file, how can the system header pollute the namespace of the application when the applications requests the information in that header? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message