> Very nice, thanks.
>
> I'm getting this error, for each built object file:
>
> $ make V=1 C=1
> [SP] ctree.o
Heh, I goofed when building the echo and actual rules, might as well
update that to $< to have it output .c?
@$(check_echo) " [SP] $@"
$(Q)$(check) $(AM_CFLAGS) $(CFLAGS) $<
:)
> sparse -include .cc-defines.h -D__CHECKER__ -D__CHECK_ENDIAN__ -Wbitwise -Wuninitialized -Wshadow -Wundef -Wall -D_FILE_OFFSET_BITS=64 -DBTRFS_FLAT_INCLUDES -fPIC -g -O1 ctree.c
> /usr/include/stdio.h:33:12: error: unable to open 'stddef.h'
> make: *** [ctree.o] Error 1
*nod*. I also ran in to this on another box. Indeed, as you said in a
later email, this comes from older sparse not knowing to add the
internal gcc include installation paths to its search path. You can
hack this yourself:
gcc_install := "$(shell gcc --print-search | \
awk '($$1 == "install:"){print $$2}')/install"
sparse -I$(gcc_install)
But honestly, I'm not sure that we should bother, given all the other
problems with older sparse. It seems acceptable to ask people to run
the latest git snapshot. It's easy.
- z
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
