public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Фёдар Стрыжнёў" <fedor_qd@mail.ru>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>, gcc-help@gcc.gnu.org
Subject: Re: Symbian: unalighned relocations for pointers-to-members
Date: Tue, 21 Dec 2021 17:01:28 +0300	[thread overview]
Message-ID: <20211221170128.76f2b59538f93aa5177b813e@mail.ru> (raw)
In-Reply-To: <20211221000015.GY614@gate.crashing.org>

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++ is major problem because it depends from libc. Therefore libsupc++ may(and probaly will) depend from libc. Symbian itself doesn't need libc. It's ordinal library in Symbian.
> Segher


-- 
Фёдар Стрыжнёў(Fiodar Stryzhniou) <fedor_qd@mail.ru>

  reply	other threads:[~2021-12-21 14:01 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       ` Фёдар Стрыжнёў [this message]
2021-12-21 14:13         ` Jonathan Wakely
2021-12-21 15:17           ` Фёдар Стрыжнёў
2021-12-21 17:05             ` Jonathan Wakely
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=20211221170128.76f2b59538f93aa5177b813e@mail.ru \
    --to=fedor_qd@mail.ru \
    --cc=Richard.Earnshaw@foss.arm.com \
    --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).