Hi Jakub,
thanks for your review. I also answered Maxim in the initial thread.
I agree we your points about not enforcing Android stuff into all
*linux* targets, but for e.g
tm_file=$tm_file linux-android.h
.. this enforcing been there before my patch and therefore it would be
better to address
On 3/09/2013, at 5:53 PM, Jakub Jelinek wrote:
On Tue, Sep 03, 2013 at 09:25:31AM +0400, Alexander Ivchenko wrote:
Several builds are broken after r201838.
What targets actually support bionic? If it is just arm, i?86/x86_64
and perhaps aarch64 and nothing else, I'd like to question the
On Wed, Sep 04, 2013 at 08:02:13PM +1200, Maxim Kuvyrkov wrote:
Nominal handling of Bionic by all *linux* targets is my fault, and it
seemed like a good thing at the time. With several iterations of
improvements laid on top of this initial decision it now becoming a mess.
I'm thinking along
Hi,
Several builds are broken after r201838.
Here is the fix, awaiting review:
http://gcc.gnu.org/ml/gcc-patches/2013-08/msg01245.html
The targets that are broken now:
1) *linux* targets that do not include config/linux.h in their tm.h
(e.g alpha-linux, ppc64-linux etc). For them we have:
