remove nosys.specs from main build as pico_libc_interface provides syscalls #3014

Merged

kilograham merged 2 commits from remove-vestigial-compiler-options into develop

2026-06-17 09:41:59 -05:00

kilograham commented

2026-06-17 00:32:57 -05:00

(Migrated from github.com)

No description provided.

will-v-pi (Migrated from github.com) approved these changes

2026-06-17 06:00:25 -05:00

projectgus commented

2026-06-23 18:53:20 -05:00

(Migrated from github.com)

FWIW I have always understood the reason for nosys.specs is to see a linker warning if you haven't implemented necessary syscalls yourself. If you don't pass this then it'll make no difference if custom syscalls are linked as intended, but it's now possible for a build to quietly link the newlib default syscall implementations instead - which might pull in a bunch of unintended dependencies or runtime behaviour.

(Maybe this doesn't matter, and also I'm not 100% sure my understanding is correct, but I thought I'd mention it.)

FWIW I have always understood the reason for `nosys.specs` is to see a linker warning if you *haven't* implemented necessary syscalls yourself. If you don't pass this then it'll make no difference if custom syscalls are linked as intended, but it's now possible for a build to quietly link the newlib default syscall implementations instead - which might pull in a bunch of unintended dependencies or runtime behaviour. (Maybe this doesn't matter, and also I'm not 100% sure my understanding is correct, but I thought I'd mention it.)

Rows
Columns