Skip to content

GitLab

Switch branch/tag
  1. 29 Jun, 2023 2 commits
    • Hongxu Jia's avatar
      bazel-native: disable uninative · f3c18c0b
      Hongxu Jia authored 
      The command bazel is a binary of a self-extracting zip file,
call patchelf-uninative on it may break it occasionally

...
bazel/bazel.real: Input/output error
...

Due to commit [89bb76dc

 bazel.bbclass: Fix build with
bazel from sstate-cache] has called patchelf-uninative on
the extracted binaries, disable uninative on bazel command
Signed-off-by: default avatarHongxu Jia <hongxu.jia@windriver.com>
      f3c18c0b
    • Hongxu Jia's avatar
      tensorflow.inc: workaround compile error for gcc 13.1 · 7ee5b543
      Hongxu Jia authored 
      
After gcc is upgraded to 13.1, a compile error:
|external/boringssl/src/crypto/bytestring/cbb.c:388:14: error: storing
the address of local variable 'child' in '*cbb.child' [-Werror=dangling-pointer=]
|  388 |   cbb->child = out_contents;
|      |   ~~~~~~~~~~~^~~~~~~~~~~~~~

Add -Wno-dangling-pointer to workaround the error

...
|tensorflow/lite/kernels/internal/spectrogram.cc:46:22: error: 'uint32_t' was not declared in this scope
|   46 | inline int Log2Floor(uint32_t n) {
      |                      ^~~~~~~~
|tensorflow/lite/kernels/internal/spectrogram.cc:20:1: note: 'uint32_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'?
...

Add '#include <cstdint>'
Signed-off-by: default avatarHongxu Jia <hongxu.jia@windriver.com>
      7ee5b543
  3. 25 Jun, 2023 1 commit
  5. 02 Jun, 2023 2 commits
    • Tomasz Dziendzielski's avatar
      bazel.bbclass: Fix build with bazel from sstate-cache · 89bb76dc
      Tomasz Dziendzielski authored 
      
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

Random errors can occur when bazel is taken from sstate-cache and the
dynamic loader is no longer available. Setting DYNAMIC_LOADER and
letting populate_sysroot_setscene modify the UNINATIVE_LOADER is not
enough. That way we just modify the loader of bazel binary, but bazel is
also a self-extracting zip file with built-in binaries that need
dynamic loader modification to work.

Eample error, as you can see it's quite misleading:
| An error occurred during the fetch of repository 'local_config_cuda'
| Cuda Configuration Error: Invalid cpu_value
| Skipping 'tensorflow/lite/tools/benchmark:benchmark_model': no such package '@local_config_cuda//cuda

To fix this in do_configure execute bazel version to unpack
output_user_root and run patchelf-uninative on the ELF executables. Then
change modification time to some future date so that bazel does not see
the modification.
Signed-off-by: default avatarTomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
      89bb76dc
    • Tomasz Dziendzielski's avatar
      bazel-native: Allow build from sstate-cache · 16f5def9
      Tomasz Dziendzielski authored 
      CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

Using TOPDIR variable breaks the sstate-cache every time build directory
changes totally breaking build from sstate-cache among different workspaces.

Changing that to TMPDIR that is included in BB_HASHEXCLUDE_COMMON.

Another thing is disabling the UNINATIVE_LOADER, causing sstate-cache
artifacts not working in different workspaces. On
populate_sysroot_setscene patchelf-uninative --set-interpreter with
empty argument is ran which does not change the interpreter path and
then bazel binary ends up with path to the interpreter that might not
exist, since the bazel was taken from sstate-cache.

Removing the UNINATIVE_LOADER = "" so that uninative.bbclass can
correctly replace the interpreter path and make bazel binary usable.
One could think that it will reintroduce the original issue behind
disabling uninative, which was some java file corrupted (see commit
dd7642b6

), but I think we don't have this problem anymore and also I
don't think it was the correct solution - since the loader is anyway
included in the binary, so it wasn't really disabling it, just disabling
the yocto functionality around uninative. If the error re-occurs I think
different solution should be found.
Signed-off-by: default avatarTomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
      16f5def9
  7. 30 May, 2023 1 commit
  9. 07 Apr, 2023 1 commit
  11. 27 Mar, 2023 1 commit
    • Hongxu Jia's avatar
      tensorflow: Fix failure while gcc <= 7.5.0 · b73c58f9
      Hongxu Jia authored 
      
Drop the revert patch, and fix the error directly

|tensorflow/compiler/mlir/quantization/tensorflow/debugging/mlir_dump.cc:93:10:
error: could not convert 'dump_file' from 'std::unique_ptr<llvm::raw_fd_ostream>'
to 'absl::lts_20220623::StatusOr<std::unique_ptr<llvm::raw_fd_ostream> >'
|   return dump_file;
          ^~~~~~~~~
Signed-off-by: default avatarHongxu Jia <hongxu.jia@windriver.com>
      b73c58f9
  13. 24 Mar, 2023 3 commits
  15. 23 Mar, 2023 4 commits
  17. 22 Mar, 2023 1 commit
  19. 21 Mar, 2023 2 commits
  21. 15 Mar, 2023 6 commits
  23. 15 Dec, 2022 6 commits
  25. 25 Nov, 2022 1 commit
    • Hongxu Jia's avatar
      tensorflow: improve python3.10 warning · 7d02ce35
      Hongxu Jia authored 
      
Other than print mess of warning message during bitbake parsing,
directly skip tensorflow recipe if python3.10 is not used, in this
situation, there will be no warning message if tensorflow is not
explicitly built

$ bitbake tensorflow
ERROR: Nothing PROVIDES 'tensorflow'
tensorflow was skipped: We shouldn't have multilib variants for tensorflow
tensorflow was skipped:
The official TensorFlow is tested and supported under Python 3.7-3.10
Please add the following to local.conf
    DISTRO_FEATURES:append = ' tensorflow'
    DISTRO_FEATURES_NATIVE:append = ' tensorflow'
    DISTRO_FEATURES_NATIVESDK:append = ' tensorflow'
It will apply python3 3.10.6 recipe
Signed-off-by: default avatarHongxu Jia <hongxu.jia@eng.windriver.com>
      7d02ce35
  27. 18 Nov, 2022 3 commits
  29. 14 Nov, 2022 3 commits
  31. 10 Nov, 2022 3 commits