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

Fix libcufile.so name to have *.0 sufix #2735

Merged
merged 1 commit into from Mar 1, 2021

Conversation

JanuszL
Copy link
Contributor

@JanuszL JanuszL commented Feb 26, 2021

  • as libcufile.so is still 0.x version it is named as .so.0, not .so.1, so fix the name of cuFile that DALI looks for

Signed-off-by: Janusz Lisiecki jlisiecki@nvidia.com

Why we need this PR?

Pick one, remove the rest

  • It fixes libcufile.so name to have *.0 sufix

What happened in this PR?

Fill relevant points, put NA otherwise. Replace anything inside []

  • What solution was applied:
    as libcufile.so is still 0.x version it is named as .so.0, not .so.1, so fix the name of cuFile that DALI looks for
  • Affected modules and functionalities:
    dynlink_cufile.cc
  • Key points relevant for the review:
    NA
  • Validation and testing:
    current test apply
  • Documentation (including examples):
    NA

JIRA TASK: [NA]

- as libcufile.so is still 0.x version it is named as .so.0, not .so.1,
  so fix the name of cuFile that DALI looks for

Signed-off-by: Janusz Lisiecki <jlisiecki@nvidia.com>
@dali-automaton
Copy link
Collaborator

CI MESSAGE: [2114880]: BUILD STARTED

@dali-automaton
Copy link
Collaborator

CI MESSAGE: [2114919]: BUILD STARTED

@dali-automaton
Copy link
Collaborator

CI MESSAGE: [2114880]: BUILD PASSED

@dali-automaton
Copy link
Collaborator

CI MESSAGE: [2114919]: BUILD PASSED

@JanuszL JanuszL merged commit b056d74 into NVIDIA:master Mar 1, 2021
@JanuszL JanuszL deleted the fix_libcufile_name branch March 1, 2021 11:18
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.

None yet

5 participants