tools/testing/selftests/nolibc/Makefile

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/nolibc/Makefile

Extension

[no extension]

Size

737 bytes

Lines

27

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: build/configuration rule

Status

atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0

TEST_GEN_PROGS := nolibc-test libc-test

include ../lib.mk
include $(top_srcdir)/scripts/Makefile.compiler

cc-option = $(call __cc-option, $(CC),,$(1),$(2))

include Makefile.include

$(OUTPUT)/nolibc-test: CFLAGS = -nostdlib -nostdinc -static \
	 -isystem $(top_srcdir)/tools/include/nolibc -isystem $(top_srcdir)/usr/include \
	 $(CFLAGS_NOLIBC_TEST)
$(OUTPUT)/nolibc-test: LDLIBS = $(if $(LLVM),,-lgcc)
$(OUTPUT)/nolibc-test: $(NOLIBC_TEST_SOURCES) | headers

$(OUTPUT)/libc-test: $(NOLIBC_TEST_SOURCES)
	$(call msg,CC,,$@)
	$(Q)$(LINK.c) $^ -o $@

help:
	@echo "For the custom nolibc testsuite use '$(MAKE) -f Makefile.nolibc'; available targets:"
	@$(MAKE) -f Makefile.nolibc help

.PHONY: help

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.