mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Tom Storey <tom@snnap.net>
To: musl@lists.openwall.com
Subject: [musl] Building for m68k
Date: Thu, 23 Apr 2020 12:05:27 +1000	[thread overview]
Message-ID: <CAFDgZgUw_KybjBsYm_+i0xSMWrajYz65DtaN=fjTTbN+sBfKsQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

Hi all.

Is anyone out there particularly familiar with building musl for the m68k?

I was able to successfully build it, but then later discovered that it
would appear to be targeting 68020+ processors more specifically. I would
like to build for the earlier 680[01]0's.

Specific examples are to do with (at least) aio where some atomic
instructions are used (e.g. cas - compare and swap) which only exist for
the 68020 and later, but not for earlier processors.

https://git.musl-libc.org/cgit/musl/tree/src/aio/aio.c#n375
https://git.musl-libc.org/cgit/musl/tree/arch/m68k/atomic_arch.h

Thus, adding -m68000 to the CFLAGS env variable when trying to do a rebuild
results in a failure complaining that the 68020+ is required. I dont know
what else is hiding away in the rest of it that will also be
incompatible... :-)

Any suggestions, pointers, tips would be greatly appreciated.

Thanks
Tom

[-- Attachment #2: Type: text/html, Size: 1273 bytes --]

             reply	other threads:[~2020-04-23  2:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23  2:05 Tom Storey [this message]
2020-04-23  2:32 ` Rich Felker
2020-04-23  5:04   ` Tom Storey
2020-04-23 16:30     ` Rich Felker
2020-04-24  0:36       ` Tom Storey
2020-04-24  0:51         ` Rich Felker
2020-04-24  1:14           ` Tom Storey
2020-04-24  1:20             ` Rich Felker
2020-04-24  2:29               ` Tom Storey
2020-04-24  2:37                 ` Rich Felker

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='CAFDgZgUw_KybjBsYm_+i0xSMWrajYz65DtaN=fjTTbN+sBfKsQ@mail.gmail.com' \
    --to=tom@snnap.net \
    --cc=musl@lists.openwall.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).