On Wed, Aug 22, 2012 at 10:09:27PM +0200, Tijl Coosemans wrote:
> On 21-08-2012 17:04, Dan McGregor wrote:
> > My solution is certainly fairly hacky, I just took inspiration from
> > NetBSD. I wanted to see if it could be done. While I was there I did
> > identify several files that should be com
I can't speak for Tijl, but being able to build anything simply by
passing -m32 to the compiler is my goal.
Did your Intel EFI work involve #defining _KERNEL anywhere?
On 22 August 2012 16:04, Eric McCorkle wrote:
> I ran into some bugs compiling things with -m32 in the intel EFI work. As
> th
On 22 August 2012 14:09, Tijl Coosemans wrote:
> On 21-08-2012 17:04, Dan McGregor wrote:
>> My solution is certainly fairly hacky, I just took inspiration from
>> NetBSD. I wanted to see if it could be done. While I was there I did
>> identify several files that should be common between i386 and
On 21-08-2012 17:04, Dan McGregor wrote:
> My solution is certainly fairly hacky, I just took inspiration from
> NetBSD. I wanted to see if it could be done. While I was there I did
> identify several files that should be common between i386 and amd64,
> such as exec.h.
>
> Since reading your em
;>>> I've been working on porting compiler-rt/clang's support for address
>>>> sanitization (asan) to FreeBSD. So far I have it building and it
>>>> appears to work properly, however the build system expects to be able
>>>> to build 32 bit binaries o
or wrote:
>>>>
>>>> Hi.
>>>>
>>>> I've been working on porting compiler-rt/clang's support for address
>>>> sanitization (asan) to FreeBSD. So far I have it building and it
>>>> appears to work properly, however the build
I have it building and it
appears to work properly, however the build system expects to be able
to build 32 bit binaries on amd64.
amd64 doesn't include i386's machine/foo headers. The included patch
is my proposed solution:
Add i386 headers to /usr/include/i386, and in machine/foo.h, ch
I have it building and it
>> > appears to work properly, however the build system expects to be able
>> > to build 32 bit binaries on amd64.
>> >
>> > amd64 doesn't include i386's machine/foo headers. The included patch
>> > is my proposed soluti
san) to FreeBSD. So far I have it building and it
>> appears to work properly, however the build system expects to be able
>> to build 32 bit binaries on amd64.
>>
>> amd64 doesn't include i386's machine/foo headers. The included patch
>> is my propose
I have it building and it
> > appears to work properly, however the build system expects to be able
> > to build 32 bit binaries on amd64.
> >
> > amd64 doesn't include i386's machine/foo headers. The included patch
> > is my proposed solution:
> >
&
to be able
> to build 32 bit binaries on amd64.
>
> amd64 doesn't include i386's machine/foo headers. The included patch
> is my proposed solution:
>
> Add i386 headers to /usr/include/i386, and in machine/foo.h, check if
> it's a 32 bit build and inclu
On 08/21/12 09:32 AM, Dan McGregor wrote:
Hi.
I've been working on porting compiler-rt/clang's support for address
sanitization (asan) to FreeBSD. So far I have it building and it
appears to work properly, however the build system expects to be able
to build 32 bit binaries on amd
Hi.
I've been working on porting compiler-rt/clang's support for address
sanitization (asan) to FreeBSD. So far I have it building and it
appears to work properly, however the build system expects to be able
to build 32 bit binaries on amd64.
amd64 doesn't include i386's
13 matches
Mail list logo
