Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: install binary and pkgsrc


> Now head binary is only v5 above.
> http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/202303021930Z/.

I think hpcarm is v4, but you're probably talking about the evbarm builds.

> But pkgsrc is v6 above. v4 have no 10 files.
> https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/
> > I think arm is v4 is common arch. I want use v4 pkgsrc.

I don't think v4 and v5 binaries are guaranteed to run correctly on v6 hardware. If I remember correctly, v6 is the first ARM architecture to add support for multi-core CPUs with CPU instructions to allow mutexes and semaphores.

Most v4 programs will work fine though.

I don't think our pkgsrc archives are configured in a way that to support the complexity of the ARM port. We really could do with builds for each of v4, v5 and v6.

It's my understanding that v4 and v5 can be run on some v6 hardware, but certain instructions that v4 and/or v5 use aren't available on newer hardware and NetBSD doesn't emulate them.

v5, which is synonymous with earm, packages won't run on v4, but v4 packages will run on v5. Since I didn't know this when I started building earm packages, I later added earmv4, which is why there are significantly fewer packages in earmv4 than earm.

Starting with NetBSD 10, I plan to have all of my older v4 / v5 compatible hardware build just v4 and let people use v4 for v5, too. I also need to see why distcc wasn't working properly with v4, since that speeds things up quite a bit.

In any case, I've recently started building 2022Q4 for NetBSD-10/earmv4, but it'll be a while before binaries start making their way to the NetBSD servers.


Home | Main Index | Thread Index | Old Index