From: Helmut Grohne <helmut@subdivi.de>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: Guillem Jover <guillem@debian.org>,
linux-snps-arc <linux-snps-arc@lists.infradead.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"980963@bugs.debian.org" <980963@bugs.debian.org>
Subject: Re: Bug#980963: dpkg: Please add ARC architecture
Date: Wed, 3 Mar 2021 20:54:14 +0100 [thread overview]
Message-ID: <YD/pZvNkKBSW53Xu@alf.mars> (raw)
In-Reply-To: <BN8PR12MB3330A43C8C7E626A24813DF2A1989@BN8PR12MB3330.namprd12.prod.outlook.com>
Hi Alexey,
On Wed, Mar 03, 2021 at 07:35:39PM +0000, Alexey Brodkin wrote:
> Well not sure why there's a dependency on glibc as w/o ARC target support
> in dpkg nothing could be built for ARC. For example I did built Binutils
> with fixed dpkg.
There is no hard dependency in that direction. Just pushback on adding
lots of Debian architectures that never really take off. For instance,
or1k was never fully bootstrapped. It'll be merged. Just not now. (Not
speaking as a dpkg maintainer here, just telling what will happen from
experience.)
> > Things that often need architecture-specific support for a new
> > architecture include:
> > * guile-X.Y (cross support)
> > * libgc
>
> Above 2 are not [yet] supported but seems to be easy ones.
guile-X.Y is quite mechanical, yes. libgc can be a little more
difficult.
> > * libxcrypt (symbols)
>
> Not sure about "libxcrypt" (whatver that means), but libgpg-error supports ARC since 2018, see:
https://tracker.debian.org/pkg/libxcrypt
> https://github.com/gpg/libgpg-error/commit/48c8f8ddfc80551db7615e1eb3555c1dc3f6a657
This should be unneeded. libgpg-error now defaults to
force_use_syscfg=no and no longer needs arch-specific changes.
> > * nspr
>
> Done in 2019, see https://hg.mozilla.org/projects/nspr/rev/cc73b6c7dab2e8053533e1f2c0c23dc721e10b76
Great.
> > * openssl (packaging)
>
> Not sure what needs to be done here as I know we build a lot of complex
> things with OpenEmbedded/Yocto and openssl libs are being built for sure.
https://sources.debian.org/src/openssl/1.1.1j-1/debian/patches/debian-targets.patch/
> > Are any of these fixed or confirmed working for arc?
>
> See above, quite some do work.
Impressive. Some work is left. What also is left is demonstrating that
it actually works. It seems that Vineet is working on integrating it.
Helmut
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2021-03-04 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <161152061283.11410.4872085138884291562.reportbug@abrodkin-5550.internal.synopsys.com>
2021-02-06 19:25 ` dpkg: Please add ARC architecture Alexey Brodkin
2021-03-03 18:04 ` Bug#980963: " Helmut Grohne
2021-03-03 18:55 ` Vineet Gupta
2021-03-03 19:35 ` Alexey Brodkin
2021-03-03 19:54 ` Helmut Grohne [this message]
2021-03-04 13:55 ` Guillem Jover
2021-03-04 23:56 ` Vineet Gupta
2021-03-26 17:39 ` Vineet Gupta
2021-05-24 20:41 ` Vineet Gupta
2021-05-28 3:50 ` Guillem Jover
2021-06-02 20:05 ` Vineet Gupta
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=YD/pZvNkKBSW53Xu@alf.mars \
--to=helmut@subdivi.de \
--cc=980963@bugs.debian.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=guillem@debian.org \
--cc=linux-snps-arc@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.