-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Makefile.bsd: remove directory that no longer exists #11077
Conversation
This was removed in a reorganization of directories preparing for the merge of FreeBSD support, 006e9a4 by mmacy. While llvm is perfectly happy with the nonexistent -I directory, the gcc6 and gcc9 we can elect to use as cross-toolchains both trip over it. Signed-off-by: Kyle Evans <[email protected]>
@mattmacy We don't use Makefile.bsd in the imports to provision anything in sys/conf/kmod.mk (OPENZFS_CFLAGS) or sys/modules/zfs/Makefile, right? Any objection to going ahead and committing the removal of these two instances of |
Codecov Report
@@ Coverage Diff @@
## master #11077 +/- ##
==========================================
- Coverage 79.67% 79.39% -0.28%
==========================================
Files 397 397
Lines 125756 125756
==========================================
- Hits 100191 99844 -347
- Misses 25565 25912 +347
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This was removed in a reorganization of directories preparing for the merge of FreeBSD support, 006e9a4 by mmacy. While llvm is perfectly happy with the nonexistent -I directory, the gcc6 and gcc9 we can elect to use as cross-toolchains both trip over it. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Ryan Moeller <[email protected]> Signed-off-by: Kyle Evans <[email protected]> Closes openzfs#11077
This was removed in a reorganization of directories preparing for the merge of FreeBSD support, 006e9a4 by mmacy. While llvm is perfectly happy with the nonexistent -I directory, the gcc6 and gcc9 we can elect to use as cross-toolchains both trip over it. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Ryan Moeller <[email protected]> Signed-off-by: Kyle Evans <[email protected]> Closes #11077
This was removed in a reorganization of directories preparing for the merge of FreeBSD support, 006e9a4 by mmacy. While llvm is perfectly happy with the nonexistent -I directory, the gcc6 and gcc9 we can elect to use as cross-toolchains both trip over it. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Ryan Moeller <[email protected]> Signed-off-by: Kyle Evans <[email protected]> Closes openzfs#11077
This was removed in a reorganization of directories preparing for the merge of FreeBSD support, 006e9a4 by mmacy. While llvm is perfectly happy with the nonexistent -I directory, the gcc6 and gcc9 we can elect to use as cross-toolchains both trip over it. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Ryan Moeller <[email protected]> Signed-off-by: Kyle Evans <[email protected]> Closes openzfs#11077
This was removed in a reorganization of directories preparing for the
merge of FreeBSD support, 006e9a4 by mmacy. While llvm is perfectly
happy with the nonexistent -I directory, the gcc6 and gcc9 we can elect
to use as cross-toolchains both trip over it.
Signed-off-by: Kyle Evans [email protected]
Motivation and Context
Description
How Has This Been Tested?
Types of changes
Checklist:
Signed-off-by
.