|
Message-ID: <5664C00A.3000106@vantagetitle.com> Date: Sun, 6 Dec 2015 18:08:58 -0500 From: Administrator <administrator@...tagetitle.com> To: musl@...ts.openwall.com Subject: Re: SPARC Support So does arch/bits/*.h define all of the kernel interfaces musl needs, or does it overwrite hard-coded defaults elsewhere in the code? I'll take a look at the aarch64 port, musl is something i'd really like to implement on our sparc machines, so this will probably be something i tackle over the next few months. On 12/6/2015 8:52 AM, Szabolcs Nagy wrote: > * Administrator <administrator@...tagetitle.com> [2015-12-06 02:01:50 -0500]: >> Is there anyone working on supporting this architecture? I am using glibc >> for now until i can get musl to compile on it. I am correct, in a perfect >> world, that all i need is to put the necessary files in /arch and fix up the >> configure script to accept the correct ARCH variable? >> > someone on irc looked at sparc about half a year ago, > but i don't know how far that got. > > git log --stat 01ef3dd9c5fa7a56aa370f244dd08e05c73010f5 > > shows which files were changed in the aarch64 port, > most of them are mandatory for a port. > >> Does the /arch dir simply override pre-existing definitions in musl, or are >> there certain files that absolutely have to be there? I see powerpc there, >> which allows me to assume that most of the work regarding endianess is >> already there. > endianness is not an issue (there is nothing in musl > that can meaningfully depend on endianness.. except > some linux syscall api structs need endian dependent > paddings, but that's target specific code). > > the real issue is that the linux kernel interfaces > for sparc have a lot of gratuitous incompatibilities > with other targets so doing arch/sparc/bits/*.h > is a significant amount of work. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.