public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Newlib <newlib@sourceware.org>
Subject: undefined reference to __ssputws_r with --specs=nano.specs
Date: Tue, 6 Feb 2024 18:40:34 +0100	[thread overview]
Message-ID: <15f5e1aa-e9a7-4a67-8eaa-b42f17f5a158@foss.st.com> (raw)

Hi,

I noticed that a lot of testcases fails when running the GCC testsuite 
with --specs=nano.specs.
Below is an example that fails with --specs=nano.specs:

$ /build/13-head-bin/bin/arm-none-eabi-g++ 
/build/gcc13_src/gcc/testsuite/g++.dg/coroutines/pr100611.C -std=c++20 
--specs=nosys.specs -o /dev/null --specs=nano.specs
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: 
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/lib/libc_nano.a(libc_a-svfwprintf.o): 
in function `_svfwprintf_r':
(.text._svfwprintf_r+0xd8): undefined reference to `__ssputws_r'
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: 
(.text._svfwprintf_r+0x834): undefined reference to `__ssputws_r'
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: 
(.text._svfwprintf_r+0x85c): undefined reference to `__ssputws_r'
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: 
(.text._svfwprintf_r+0x8a8): undefined reference to `__ssputws_r'
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: 
(.text._svfwprintf_r+0x8dc): undefined reference to `__ssputws_r'
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: 
/build/13-head-bin/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/lib/libc_nano.a(libc_a-svfwprintf.o):(.text._svfwprintf_r+0x900): 
more undefined references to `__ssputws_r' follow
collect2: error: ld returned 1 exit status


The newlib nano is configured with:

--disable-newlib-supplied-syscalls
--enable-newlib-reent-check-verify
--enable-newlib-reent-small
--enable-newlib-retargetable-locking
--disable-newlib-fvwrite-in-streamio
--disable-newlib-fseek-optimization
--disable-newlib-wide-orient
--enable-newlib-nano-malloc
--disable-newlib-unbuf-stream-opt
--enable-lite-exit
--enable-newlib-global-atexit
--enable-newlib-nano-formatted-io
--disable-nls


Is it expected that the symbol __ssputws_r is referenced but not 
provided when (I presume this is the reason) 
--enable-newlib-nano-formatted-io and --disable-newlib-wide-orient is used?

Kind regards,
Torbjörn

             reply	other threads:[~2024-02-06 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 17:40 Torbjorn SVENSSON [this message]
2024-02-15 15:19 ` Torbjorn SVENSSON
2024-02-19 16:20   ` Richard Earnshaw (lists)
2024-02-23 15:31     ` [PATCH] libc/stdio: Remove wchar_t functions from NEWLIB_NANO_FORMATTED_IO Torbjörn SVENSSON
2024-02-23 16:05       ` R. Diez
2024-03-09  8:15       ` [PATCH v2] " Torbjörn SVENSSON
2024-03-11 10:30         ` Corinna Vinschen

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=15f5e1aa-e9a7-4a67-8eaa-b42f17f5a158@foss.st.com \
    --to=torbjorn.svensson@foss.st.com \
    --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).