Lines Matching full:sysroot

46 #  will allow all further calls to gcc to be made using --sysroot
53 #  with a number of arguments (sysroot/march/mtune/..) hardcoded,
290 #   - copying the toolchain sysroot to $(STAGING_DIR)
293 # Details about sysroot directory selection.
295 # To find the sysroot directory, we use the trick of looking for the
297 # mangling the path to find the base directory of the sysroot.
299 # Note that we do not use the -print-sysroot option, because it is
304 # multilib variant (such as -march) as we want the "main" sysroot,
307 # path of the cross-compiler, without the --sysroot=$(STAGING_DIR),
309 # sysroot. This "main" sysroot directory is stored in SYSROOT_DIR.
313 # by the toolchain. So we need to find the particular sysroot we're
316 # To do so, we ask the compiler where its sysroot is by passing all
317 # flags (including -march and al.), except the --sysroot flag since we
318 # want to the compiler to tell us where its original sysroot
326 # present in the main sysroot, and only the libraries are available in
327 # each variant-specific sysroot directory.
330 # toolchain_find_sysroot returns the sysroot location for the given
357 # Integration of the toolchain into Buildroot: find the main sysroot
358 # and the variant-specific sysroot, then copy the needed libraries to
359 # the $(TARGET_DIR) and copy the whole sysroot (libraries and headers)
364 # SYSROOT_DIR:          the main sysroot directory, deduced from the location of
369 # ARCH_SYSROOT_DIR:     the sysroot of the selected multilib variant,
382 # ARCH_SUBDIR:          the relative location of the sysroot of the selected
383 #                       multilib variant compared to the main sysroot.
388 #                       libgcc_s, etc.) outside of the sysroot. In
393 #                       our sysroot, and the directory will also be
452 	$(call MESSAGE,"Copying external toolchain sysroot to staging...") ; \