On Wed, Sep 14, 2011 at 8:23 PM, Arnaud Lacombe wrote:
> Hi,
...
> ping, Warner ?
>
> FWIW, I guess that in 4 months, either you had time to finish the
> patch, or I could have found to time to complete it myself based on
> your incomplete version. I'd really be interested to benchmark recent,
>
Hi,
On Fri, Jul 8, 2011 at 5:16 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Sat, Jun 25, 2011 at 2:01 PM, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Mon, Jun 6, 2011 at 5:37 PM, Arnaud Lacombe wrote:
>>> Hi,
>>>
>>> On Tue, May 31, 2011 at 12:23 PM, Warner Losh wrote:
On May 22, 2011, at 9:48
Hi,
On Sat, Jun 25, 2011 at 2:01 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Jun 6, 2011 at 5:37 PM, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Tue, May 31, 2011 at 12:23 PM, Warner Losh wrote:
>>>
>>> On May 22, 2011, at 9:48 PM, Arnaud Lacombe wrote:
>>>
Hi Warner,
On Sat, Apr 2, 20
Hi,
On Mon, Jun 6, 2011 at 5:37 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Tue, May 31, 2011 at 12:23 PM, Warner Losh wrote:
>>
>> On May 22, 2011, at 9:48 PM, Arnaud Lacombe wrote:
>>
>>> Hi Warner,
>>>
>>> On Sat, Apr 2, 2011 at 6:49 PM, Warner Losh wrote:
On Apr 2, 2011, at 1:10 PM, Ro
Hi,
On Tue, May 31, 2011 at 12:23 PM, Warner Losh wrote:
>
> On May 22, 2011, at 9:48 PM, Arnaud Lacombe wrote:
>
>> Hi Warner,
>>
>> On Sat, Apr 2, 2011 at 6:49 PM, Warner Losh wrote:
>>>
>>> On Apr 2, 2011, at 1:10 PM, Robert N. M. Watson wrote:
>>>
On 2 Apr 2011, at 19:47, Warner Losh wr
On May 22, 2011, at 9:48 PM, Arnaud Lacombe wrote:
> Hi Warner,
>
> On Sat, Apr 2, 2011 at 6:49 PM, Warner Losh wrote:
>>
>> On Apr 2, 2011, at 1:10 PM, Robert N. M. Watson wrote:
>>
>>> On 2 Apr 2011, at 19:47, Warner Losh wrote:
>>>
> (2) Working clang/LLVM cross-compile of FreeBSD. T
Hi Warner,
On Sat, Apr 2, 2011 at 6:49 PM, Warner Losh wrote:
>
> On Apr 2, 2011, at 1:10 PM, Robert N. M. Watson wrote:
>
>> On 2 Apr 2011, at 19:47, Warner Losh wrote:
>>
(2) Working clang/LLVM cross-compile of FreeBSD. This seems like a basic
requirement to adopt clang/LLVM, and as
On Apr 2, 2011, at 1:10 PM, Robert N. M. Watson wrote:
> On 2 Apr 2011, at 19:47, Warner Losh wrote:
>
>>> (2) Working clang/LLVM cross-compile of FreeBSD. This seems like a basic
>>> requirement to adopt clang/LLVM, and as far as I'm aware that's not yet a
>>> resolved issue?
>>
>> 0 work h
On 2 Apr 2011, at 19:47, Warner Losh wrote:
>> (2) Working clang/LLVM cross-compile of FreeBSD. This seems like a basic
>> requirement to adopt clang/LLVM, and as far as I'm aware that's not yet a
>> resolved issue?
>
> 0 work has been done here to my knowledge. The world view for clang and
On Apr 2, 2011, at 12:29 PM, Robert Watson wrote:
> On Wed, 30 Mar 2011, Warner Losh wrote:
>
>> On Mar 30, 2011, at 9:23 AM, Dimitry Andric wrote:
>>> This is a rather nasty hack, though. If we can make it work, we should
>>> probably try using --sysroot instead, or alternatively, -nostdinc a
On Wed, 30 Mar 2011, Warner Losh wrote:
On Mar 30, 2011, at 9:23 AM, Dimitry Andric wrote:
This is a rather nasty hack, though. If we can make it work, we should
probably try using --sysroot instead, or alternatively, -nostdinc and
adding include dirs by hand. The same for executable and lib
On Mar 30, 2011, at 9:23 AM, Dimitry Andric wrote:
> This is a rather nasty hack, though. If we can make it work, we should
> probably try using --sysroot instead, or alternatively, -nostdinc and
> adding include dirs by hand. The same for executable and library search
> paths, although I am not
On 2011-03-30 17:26, Nathan Whitehorn wrote:
...
During the bootstrap stage, a copy of gcc (or clang) is built, that has
all default search paths for headers, libraries, etc, set relative to
${WORLDTMP}, usually /usr/obj/usr/src/tmp.
...
Since you need to build two compilers anyway (one for the
On 03/30/11 10:23, Dimitry Andric wrote:
On 2011-03-29 23:20, m...@freebsd.org wrote:
So here's what I'm pondering. When I build a library, like e.g. libc,
where do the include files get pulled from? They can't (shouldn't) be
the ones in /usr/include, but I don't see a -nostdinc like for the
k
On 2011-03-29 23:20, m...@freebsd.org wrote:
So here's what I'm pondering. When I build a library, like e.g. libc,
where do the include files get pulled from? They can't (shouldn't) be
the ones in /usr/include, but I don't see a -nostdinc like for the
kernel. There are -I directives in the Mak
Hi,
On Wed, Mar 30, 2011 at 8:00 AM, John Baldwin wrote:
> On Tuesday, March 29, 2011 5:20:30 pm m...@freebsd.org wrote:
>> I thought I knew something about how the compiler looks for include
>> files, but now I think maybe I don't know much. :-)
>>
>> So here's what I'm pondering. When I build
On Tuesday, March 29, 2011 5:20:30 pm m...@freebsd.org wrote:
> I thought I knew something about how the compiler looks for include
> files, but now I think maybe I don't know much. :-)
>
> So here's what I'm pondering. When I build a library, like e.g. libc,
> where do the include files get pull
I thought I knew something about how the compiler looks for include
files, but now I think maybe I don't know much. :-)
So here's what I'm pondering. When I build a library, like e.g. libc,
where do the include files get pulled from? They can't (shouldn't) be
the ones in /usr/include, but I don'
18 matches
Mail list logo
