From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Фёдар Стрыжнёў" <fedor_qd@mail.ru>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
gcc-help <gcc-help@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Subject: Re: Symbian: unalighned relocations for pointers-to-members
Date: Tue, 21 Dec 2021 17:05:07 +0000 [thread overview]
Message-ID: <CAH6eHdTvcnQqGLb03qOy_ZyXaR_b4WVF0Dt80UFUKv1HEevtHQ@mail.gmail.com> (raw)
In-Reply-To: <20211221181701.54fac46c566d1019e57fdf23@mail.ru>
On Tue, 21 Dec 2021, 15:17 Фёдар Стрыжнёў, <fedor_qd@mail.ru> wrote:
> On Tue, 21 Dec 2021 14:13:45 +0000
> Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
> > On Tue, 21 Dec 2021, 14:02 Фёдар Стрыжнёў (Fiodar Stryzhniou) via
> Gcc-help,
> > <gcc-help@gcc.gnu.org> wrote:
> >
> > > On Mon, 20 Dec 2021 18:00:16 -0600
> > > Segher Boessenkool <segher@kernel.crashing.org> wrote:
> > >
> > > > On Mon, Dec 20, 2021 at 10:30:01PM +0300, Фёдар Стрыжнёў (Fiodar
> > > Stryzhniou) via Gcc-help wrote:
> > > > > On Mon, 20 Dec 2021 15:37:26 +0000
> > > > > Richard Earnshaw <Richard.Earnshaw@foss.arm.com> wrote:
> > > > > > I don't think I've seen a question about SymbianOS support in
> over 5
> > > > > > years, now, possibly longer. Given that SymbianOS itself was
> > > > > > discontinued back around 2013 (8 years ago now), the GCC port has
> > > > > > declined to the point where I suspect it's likely to get
> deprecated
> > > > > > soon, due to lack of maintenance.
> > > > >
> > > > > There several configure problems but result is good. It just works.
> > > This is offtopic but can be continued in separate thread.
> > > >
> > > > Such things are never off-topic :-)
> > > >
> > > > Someone needs to do maintenance on the port. An important first
> step is
> > > > to regularly (and at least semi-frequently) post testresults. That
> also
> > > > shows everyone there is still some interest in the port, and
> importantly
> > > > it shows what the current state is.
> > > >
> > > >
> > > I wrote in email all build issues later. I need to build GCC 11 again
> to
> > > gather info.
> > > Libsupc++ tied to libstdc++
> >
> >
> > What do you mean "tied to"?
>
> I can't build libsupc++ without call "make something_command_for_libsupc"
> because got error because libstdc++ builds together with libsupc. I can't
> remember command's name. I build many releases from GCC 5.4.0 till 11.2.0.
> Errors always same.
>
Maybe if you report a bug we can help. If you can't even tell us what the
error is, nobody can help.
next prev parent reply other threads:[~2021-12-21 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 0:39 Фёдар Стрыжнёў
2021-12-19 9:35 ` Фёдар Стрыжнёў
2021-12-20 15:37 ` Richard Earnshaw
2021-12-20 19:30 ` Фёдар Стрыжнёў
2021-12-21 0:00 ` Segher Boessenkool
2021-12-21 14:01 ` Фёдар Стрыжнёў
2021-12-21 14:13 ` Jonathan Wakely
2021-12-21 15:17 ` Фёдар Стрыжнёў
2021-12-21 17:05 ` Jonathan Wakely [this message]
2021-12-29 11:04 ` Фёдар Стрыжнёў
2022-01-04 13:01 ` Richard Earnshaw
2022-01-16 11:52 ` Фёдар Стрыжнёў
2022-01-18 10:14 ` Richard Earnshaw
2022-01-21 14:17 ` Фёдар Стрыжнёў
2022-01-21 15:08 ` Richard Earnshaw
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=CAH6eHdTvcnQqGLb03qOy_ZyXaR_b4WVF0Dt80UFUKv1HEevtHQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=fedor_qd@mail.ru \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/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).