Hi,
the issue is pure header include order and include_next related. There
is no need
to mail the VM, I can reproduce it. It's just that I thought from a
glibc based
test build it would be globally fixed now, but I also already have a
uclibc build
with the error.
I now debugged something else for a client already this night and we have
guests this weekend. But this issue is very high on my TODO list now to
look at next.
Schönes Wochenende,
René
Marian Aldenhövel wrote:
Hi,
I'll continue to debug this issue later, maybe tonight. Patches
welcome, though :-)
Unfortunately I have no idea where to start. If there is anything you
want
me to try or check, just tell me.
I am building in a VM, about 1.2 GB in size. I can burn and mail that
if it
should be of any help...
(Technically I am on holiday for two weeks now. In the middle of nowwhere
but equipped with a borrowed mobile connection. So in practice I propably
really get some work done :-))
Ciao, MM
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2
