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 Pygloo Error: pygloo/hiredis/include/hiredis is a dangling symbolic link #27

Open
TRSWNCA opened this issue Mar 28, 2024 · 1 comment

Comments

@TRSWNCA
Copy link

TRSWNCA commented Mar 28, 2024

When I was building pygloo from source, dangling symbolic link error occurs. And I didn't find any file indecating the problem of pygloo/hiredis/include/hiredis. Here is my log.

(base) ➜  pygloo-main python setup.py build
running build
running build_py
running egg_info
writing pygloo.egg-info/PKG-INFO
writing dependency_links to pygloo.egg-info/dependency_links.txt
writing top-level names to pygloo.egg-info/top_level.txt
reading manifest file 'pygloo.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'pygloo.egg-info/SOURCES.txt'
running build_ext
INFO: Analyzed 5 targets (81 packages loaded, 7510 targets configured).
ERROR: /home/cyc/hpc/pygloo-test/pygloo-main/pygloo/BUILD:19:5: Error while validating output TreeArtifact File:[[<execution_root>]bazel-out/k8-fastbuild/bin]pygloo/hiredis/include/hiredis : Child read.h of tree artifact /home/cyc/.cache/bazel/_bazel_cyc/58be26f938b2b5ddf0a0de3d0c123a12/execroot/_main/bazel-out/k8-fastbuild/bin/pygloo/hiredis/include/hiredis is a dangling symbolic link
ERROR: /home/cyc/hpc/pygloo-test/pygloo-main/pygloo/BUILD:19:5: CcGnumakeMakeRule pygloo/hiredis/include/hiredis failed: not all outputs were created or valid

I'm using Ubuntu 20.04LTS, bazel 7.1.1 and Python 3.9.13. Thanks for reviewing.

By the way, I'm wondering whether this repo is still under maintenance? I didnt' find wheels supporting python3.9 and little examples of pygloo on ray were found.

@jovany-wang
Copy link
Contributor

@TRSWNCA Is this issue still there?

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