Lines Matching refs:specific

38 	   --- 6.5 Architecture-specific boot images
76 architecture-specific information to the top Makefile.
234 	combined in a built-in.o for that specific directory.
370 	Another example are the architecture-specific Makefiles which
453 	as-instr checks if the assembler reports a specific instruction
520 	cc-version is useful when a specific $(CC) version is faulty in one
551 	One typical use-case is when a specific GCC version is broken.
552 	cc-fullversion points out a more specific version than cc-version does.
561 	In this example for a specific GCC version the build will error out
671 	When compiling host programs, it is possible to set specific flags.
681 	To set specific flags for a single file the following construction
830 6) Finally, the architecture-specific part does any required post processing
851 	LDFLAGS_MODULE is used to set specific flags for $(LD) when
922     KBUILD_AFLAGS_KERNEL	$(AS) options specific for built-in
929 	$(KBUILD_AFLAGS_MODULE) is used to add arch-specific options that
933     KBUILD_CFLAGS_KERNEL	$(CC) options specific for built-in
940 	$(KBUILD_CFLAGS_MODULE) is used to add arch-specific options that
946 	$(KBUILD_LDFLAGS_MODULE) is used to add arch-specific options
996 	corresponding arch-specific section for modules; the module-building
1012 	and arch/$(ARCH)/Makefile only adds architecture-specific directories.
1021 --- 6.5 Architecture-specific boot images
1048 	There are no rules for naming architecture-specific targets,
1124 	Link target. Often, LDFLAGS_$@ is used to set specific options to ld.
1224 	CPPFLAGS_$(@F)  : Target-specific flags.
1229 	architecture-specific files.
1245 - drop kernel-specific annotations
1363 	Use this for architecture-specific install targets.