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

Revert "Make uv and nng private and static (#323)" #336

Merged
merged 1 commit into from
Nov 26, 2024
Merged

Conversation

broskoTT
Copy link
Contributor

This reverts commit 0a41bf5.

Issue

No issue

Description

This change broke tt-metal build.
post commit workflow failing: https://github.com/tenstorrent/tt-metal/actions/runs/12031721201
post commit workflow on this branch: https://github.com/tenstorrent/tt-metal/actions/runs/12032379476/job/33545486354
blackhole post-commit failing: https://github.com/tenstorrent/tt-metal/actions/runs/12031811999
blackhole post-commit on this branch: https://github.com/tenstorrent/tt-metal/actions/runs/12032509241

List of the changes

Testing

see description

API Changes

@broskoTT broskoTT enabled auto-merge (squash) November 26, 2024 14:59
@broskoTT broskoTT merged commit db8a0d5 into main Nov 26, 2024
19 of 22 checks passed
@broskoTT broskoTT deleted the brosko/revert2 branch November 26, 2024 15:00
@blozano-tt
Copy link
Collaborator

blozano-tt commented Nov 27, 2024

I am not understanding how the linked failing jobs have anything to do with this PR.

Is it obvious to you?

I see strange pipeline/machine issues ... like "lock file exists" ...

  Error: fatal: Needed a single revision
  Unable to find current revision in submodule path 'tt_metal/third_party/pybind11'
  Error: The process '/usr/bin/git' failed with exit code 1

broskoTT added a commit that referenced this pull request Dec 2, 2024
### Issue
Original PR was #323, then the reverted one was #336

### Description
libnng.so is no longer a public dependency as of this PR:
#224
Additionally, given that it is only consumed here it would be
advantageous to statically link it.
Why?
So we don't have to:
- Install it
- Package it in a debian
- Bundle it in a ttnn python wheel ... etc ... 

Along the above lines, I don't want to run into issues like this:
```
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 185, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib/python3.8/runpy.py", line [11](https://github.com/tenstorrent/tt-metal/actions/runs/11964313949/job/33356936955#step:6:12)1, in _get_module_details
    __import__(pkg_name)
  File "/home/ubuntu/actions-runner/_work/tt-metal/tt-metal/tests/end_to_end_tests/env/lib/python3.8/site-packages/ttnn/__init__.py", line 20, in <module>
    import ttnn._ttnn
ImportError: libnng.so.1: cannot open shared object file: No such file or directory
```
### List of the changes
Build nng as static
Make it private linkage

### Testing
Hoping CI is good enough

### API Changes
There are no API changes in this PR.

---------

Co-authored-by: Bryan Wilder Field Lozano <[email protected]>
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

Successfully merging this pull request may close these issues.

3 participants