Date: Wed, 27 Mar 2002 22:14:20 +0100 From: Thomas =?iso-8859-1?q?W=FCrfl?= <ThomasWuerfl@gmx.de> To: "Karsten W. Rohrbach" <karsten@rohrbach.de> Cc: freebsd-hackers@freebsd.org Subject: Re: problems with wine Message-ID: <16qKkP-0zWHOSC@fmrl10.sul.t-online.com> In-Reply-To: <20020327211845.H43825@mail.webmonster.de> References: <20020327203941.F43825@mail.webmonster.de> <Pine.BSF.4.21.0203271142430.47944-100000@InterJet.elischer.org> <20020327211845.H43825@mail.webmonster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Mittwoch, 27. März 2002 21:18 schrieben Sie: > Julian Elischer(julian@elischer.org)@2002.03.27 11:43:50 +0000: > [...my dumbass workaround deleted...] > > > He said he was running native.. > > > > the cpu type is in > > `sysctl hw` > > The code shuold be altered on FreeBSD to look there. > > oops, you're prefectly right. i skipped the "(native)" when reading the > original mail. anyway, wine needs to be patched then, since hw.machine > gives the platform which is "i386" in case of x86, correct? btw, is this > intended behaviour? i thought hw.machine_arch would be for that purpose. > > hw.machine_arch is set up in kern/kern_mib.c to "i386" on pc hardware > hw.machine is set up in i386/i386/identcpu.c to "i386" anytime (on > 4.3-stable, my currently active stable source i have immediate access > to) wouldn't it make sense to set the SYSCTL_STRING on hw.machine to a > gcc compatible (-mcpu or -march) value? this would make us happier in > the future when gcc does not generate broken code in several scenarios > anymore. does this make sense? > > /k Afaik 'hw.machine' is system architecture (i386=IA32). But in 'sysctl hw' is no _cpu_type_ like in linux-proc/cpuinfo. I'll have a look at the linuxulator source... ;-) Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16qKkP-0zWHOSC>