Hi,
I wrote:
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 debugg
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 el
Hi,
Marian Aldenhövel wrote:
Hi,
Ok, this was not uclibc's fault, but a generic G++ (STL) cross compile
regression (in the upstream, GCC header files).
Apparently this still is an C++-issue unrelated to libusb. I have a
custom
program packaged for T2 now that is written in C++. And it show
Hi,
Ok, this was not uclibc's fault, but a generic G++ (STL) cross compile
regression (in the upstream, GCC header files).
Apparently this still is an C++-issue unrelated to libusb. I have a custom
program packaged for T2 now that is written in C++. And it shows a similar
problem regarding std
Hi,
Ok, this was not uclibc's fault, but a generic G++ (STL) cross compile
regression (in the upstream, GCC header files).
This should be addressed with r30044.
Unfortunately not. ERROR-LOG is attached. To confirm it was not a mixup
I also tried a complete build.
stdarg.h exists as:
[EMAIL
Hi,
Marian Aldenhövel wrote:
Hi,
I noticed this uclibc related build error, likewise. If you do not need
the libusb C++ binding you could configure libusb in your target
with --disable-cxx (or so)
I'll try that. To be honest I don't know whether I need them as I'm only
building it as requir
Hi,
Marian Aldenhövel wrote:
Hi,
I updated to HEAD again and tried to rebuild. Libusb fails in a way
that I do not understand. Can you please help me make sense of it?
Ciao, MM
I noticed this uclibc related build error, likewise. If you do not need
the libusb C++ binding you could configur
