https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78110
Bernd Edlinger changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78110
--- Comment #5 from Bernd Edlinger ---
Author: edlinger
Date: Wed Oct 26 17:26:00 2016
New Revision: 241591
URL: https://gcc.gnu.org/viewcvs?rev=241591&root=gcc&view=rev
Log:
2016-10-26 Bernd Edlinger
PR libstdc++/78110
* lib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78110
--- Comment #4 from Bernd Edlinger ---
First I was a bit shocked, but i think my patch above looks reasonable.
Because the installation is free-standing it is natural that we
cannot #include . Although the eCos has no memalign,
that is benign,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78110
--- Comment #3 from Jonathan Wakely ---
(In reply to Bernd Edlinger from comment #1)
> oh, I am using eCos and that is based on newlib but on a very very old one.
> I don't know what happens when I dont use --with-newlib, but I can try...
>
> co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78110
--- Comment #2 from Bernd Edlinger ---
without --with-newlib the build fails miserably...
this works for me:
--- libstdc++-v3/libsupc++/new_opa.cc.orig 2016-09-16 20:09:14.0
+0200
+++ libstdc++-v3/libsupc++/new_opa.cc 2016-10-26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78110
--- Comment #1 from Bernd Edlinger ---
oh, I am using eCos and that is based on newlib but on a very very old one.
I don't know what happens when I dont use --with-newlib, but I can try...
configure.ac has this:
# First, test for "known" syste
