From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>, Steve Ellcey <sellcey@caviumnetworks.com>
Subject: Re: [PATCH] Fix sparc build due missing __WORDSIZE_TIME64_COMPAT32 definition (committed)
Date: Fri, 04 Nov 2016 21:25:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611042122480.19848@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1478290761-7603-1-git-send-email-adhemerval.zanella@linaro.org>
On Fri, 4 Nov 2016, Adhemerval Zanella wrote:
> 1. Remove 32 bits definition form 64 bits headers and vice versa.
> For instance, powerpc32 and sparc32 linux wordsize contains
> checks for 64 bits definition and ideally 32 bit build should
> not include such header.
>
> 2. Linux definition could include-next default definition instead
> of replicate its value.
Installed headers have to be suitable for all multilibs in multiarch cases
and cannot #include_next other variants of that header. The files
sysdeps/sparc/sparc32/bits/wordsize.h and
sysdeps/sparc/sparc64/bits/wordsize.h and
sysdeps/powerpc/powerpc32/bits/wordsize.h and
sysdeps/powerpc/powerpc64/bits/wordsize.h are unused.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-04 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 20:19 Adhemerval Zanella
2016-11-04 21:25 ` Joseph Myers [this message]
2016-11-04 21:33 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1611042122480.19848@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=sellcey@caviumnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).