Am Wed, 29 Oct 2014 13:39:33 +0100
schrieb Luca Barbato :
> On 27/10/14 12:07, M. Ziebell wrote:
> > Does clang compile glibc already?
> > At the last GNU Cauldron the speaker said that clang fails because
> > of:[1]
> > - nested functions
> > - VLAIS
> >
> > How did you avoid that problem?
>
> m
On 27/10/14 12:07, M. Ziebell wrote:
Does clang compile glibc already?
At the last GNU Cauldron the speaker said that clang fails because
of:[1]
- nested functions
- VLAIS
How did you avoid that problem?
musl is known to work fine.
Am 27. Oct 2014, 12:07 schrieb "M. Ziebell" :
> Does clang compile glibc already?
> At the last GNU Cauldron the speaker said that clang fails because
> of:[1]
> - nested functions
> - VLAIS
>
> How did you avoid that problem?
Even without this issues there remains the fact that glibc is quite
c
Am 27. Oct 2014, 11:14 schrieb Alexis Ballier :
> By the way, any help for maintaining the libc++ stack is very welcome;
> as you can see from the age of the current snapshots, it's been some
> time I've not been playing with it.
>
>
> Some notes:
> - why not adding a clang subprofile ? there's o
On Mon, 27 Oct 2014 12:29:40 +0100
"M. Ziebell" wrote:
> Am Mon, 27 Oct 2014 12:10:51 +0100
> schrieb Alexis Ballier :
>
> > On Mon, 27 Oct 2014 12:07:25 +0100
> > "M. Ziebell" wrote:
> >
> > > Does clang compile glibc already?
> > > At the last GNU Cauldron the speaker said that clang fails b
Am Mon, 27 Oct 2014 12:10:51 +0100
schrieb Alexis Ballier :
> On Mon, 27 Oct 2014 12:07:25 +0100
> "M. Ziebell" wrote:
>
> > Does clang compile glibc already?
> > At the last GNU Cauldron the speaker said that clang fails because
> > of:[1]
> > - nested functions
> > - VLAIS
> >
> > How did yo
On Mon, 27 Oct 2014 12:07:25 +0100
"M. Ziebell" wrote:
> Does clang compile glibc already?
> At the last GNU Cauldron the speaker said that clang fails because
> of:[1]
> - nested functions
> - VLAIS
>
> How did you avoid that problem?
by using freebsd's libc :)
only problem I can recall is
Does clang compile glibc already?
At the last GNU Cauldron the speaker said that clang fails because
of:[1]
- nested functions
- VLAIS
How did you avoid that problem?
Marco
[1]
http://www.youtube.ca/watch?v=mmiDwKgn6Ho&list=PLOGTP9W1DX5U53pPxtWdKkyiqe3GAn6Nd
Am Mon, 27 Oct 2014 11:20:00 +0100
Alexis Ballier wrote:
> - why not adding a clang subprofile ? there's one for amd64-fbsd; I had
> been able to build a complete stage 3 without too much trouble.
> There's probably nothing bsd specific there, so moving
> generic code from there to profiles/features should work.
I'd try to te
By the way, any help for maintaining the libc++ stack is very welcome;
as you can see from the age of the current snapshots, it's been some
time I've not been playing with it.
Some notes:
- why not adding a clang subprofile ? there's one for amd64-fbsd; I had
been able to build a complete stage
>
> Could you please blog or add some notes to the wiki about it?
>
I've put up a preliminary version for the toolchain part:
https://gist.github.com/tamiko/7e3a0be806fac11f2a35
Best,
Matthias
11 matches
Mail list logo
