public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: jdoubleu <hi@jdoubleu.de>, newlib@sourceware.org
Subject: Re: Does newlib support x86_64-pc-linux-gnu?
Date: Sat, 14 May 2022 12:20:57 -0700	[thread overview]
Message-ID: <87r14vnco6.fsf@keithp.com> (raw)
In-Reply-To: <5027bd1e-f976-fd55-dd70-f86cc805d969@jdoubleu.de>

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

jdoubleu <hi@jdoubleu.de> writes:

> I'm trying to run the testsuite on my linux host. Right now, all tests 
> are linked against glibc, causing me to test glibc instead of newlib.
>
> This would really help me testing newlib, because I don't have any 
> "special" hardware, nor emulators setup. It does also offer the 
> possibility to test newlib farily easy in a CI.

It's possible, and picolibc (a newlib fork) uses this in it's CI
setup. What you do is link newlib *before* glibc so that you pull in the
newlib upper-level functions and then use glibc for the syscalls.

It does make some development easier, but there are places which are a
bit funky -- the 'stat' syscall, in particular, where you need to
declare struct stat so that it matches glibc but without using glibc
headers (as you'll be compiling against newlib headers).

It's not that hard to use an arm or risc-v emulator with semihosting
support to test the library though, and that avoids issues like that.

-- 
-keith

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-05-14 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 12:50 jdoubleu
2022-05-14 19:20 ` Keith Packard [this message]
2022-05-17 11:13   ` jdoubleu

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=87r14vnco6.fsf@keithp.com \
    --to=keithp@keithp.com \
    --cc=hi@jdoubleu.de \
    --cc=newlib@sourceware.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).