Skip to content
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

Build Failure During make all and make bootstrapper #20

Open
LivingXu opened this issue Aug 27, 2024 · 1 comment
Open

Build Failure During make all and make bootstrapper #20

LivingXu opened this issue Aug 27, 2024 · 1 comment

Comments

@LivingXu
Copy link

Issue: Build Failure During make all and make bootstrapper

Description

I encountered a build failure while attempting to compile the project using both the make all and make bootstrapper commands. Below are the detailed outputs from the terminal:

Output from make all:

scion@student-net-cx-0052 bootstrapper % make all
rm -f bin/*
./.bazel-build-env
STABLE_PKG_VERSION_SCION_BOOTSTRAPPER v0.0.0-v0.0.7-2-g95649ef
bazel build //:bootstrapper
WARNING: --enable_bzlmod is set, but no MODULE.bazel file was found at the workspace root. Bazel will create an empty MODULE.bazel file. Please consider migrating your external dependencies from WORKSPACE to MODULE.bazel. For more details, please refer to https://github.com/bazelbuild/bazel/issues/18958.
ERROR: /private/var/tmp/_bazel_scion/bcece009ef9f5ef3c4275fb90bb2a8b1/external/io_bazel_rules_go/BUILD.bazel:71:16: in (an implicit dependency) attribute of go_context_data rule @@io_bazel_rules_go//:go_context_data: in $whitelist_function_transition attribute of go_context_data rule @@io_bazel_rules_go//:go_context_data: package group '@@bazel_tools//tools/whitelists/function_transition_whitelist:function_transition_whitelist' is misplaced here (they are only allowed in the visibility attribute)
ERROR: /private/var/tmp/_bazel_scion/bcece009ef9f5ef3c4275fb90bb2a8b1/external/io_bazel_rules_go/BUILD.bazel:71:16: Analysis of target '@@io_bazel_rules_go//:go_context_data' failed
ERROR: Analysis of target '//:bootstrapper' failed; build aborted: Analysis failed
INFO: Elapsed time: 1.892s, Critical Path: 0.06s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
FAILED: 
    Fetching repository @@com_github_inconshreveable_log15; starting
    Fetching repository @@bazel_gazelle_go_repository_config; starting
    Fetching repository @@org_golang_x_net; starting
    Fetching repository @@com_github_pelletier_go_toml; starting
    Fetching repository @@com_github_insomniacslk_dhcp; starting
    Fetching repository @@com_github_miekg_dns; starting
    Fetching repository @@com_github_mdlayher_ndp; starting
    Fetching repository @@com_github_grandcat_zeroconf; starting ... (9 fetches)
make: *** [bazel] Error 1

Output from make bootstrapper:

No target named 'bootstrapper' in the Makefile.

scion@student-net-cx-0052 bootstrapper % make bootstrapper
make: *** No rule to make target `bootstrapper’.  Stop.

Environment

  • Operating System: macOS Sonoma V14.6(23G80)
  • Bazelisk version: 1.20.0
  • Bazel Version: 7.3.1
  • make Version: 3.81

Steps to Reproduce

  • Clone the repository.
  • Run the command make all and make bootstrapper in the project root.

Additional Information

  • I have not modified any of the build files.
@FR4NK-W
Copy link
Contributor

FR4NK-W commented Nov 22, 2024

Thank you @LivingXu for providing all the relevant details 👍

Here are the points which stuck out:

Environment
Operating System: macOS Sonoma V14.6(23G80)

Steps to Reproduce
Run the command make all and make bootstrapper in the project root.

Please note, from the README.md:
https://github.com/netsec-ethz/bootstrapper?tab=readme-ov-file#building

Experimental availability is also provided for macOS and Windows. Run make darwin [...]

Does the build succeed if you follow the instruction in the README?

Is there any particular reason you want / need to build with Bazel?
As mentioned, on macOS, we provide a separate build target where we directly build with the go tool, since we do not provide packaging for that platform.

We could add feature detection / OS detection to the main make targets. Would that satisfy your use case?
The reason for providing separate targets for the OSes with experimental support was to enable easy cross-compiling.
Is your goal to cross-compile for linux from a macOS host?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants