1. 31 May, 2024 1 commit
    • Joanne Hugé's avatar
      software/ors-amarisoft: add support for IMS · 18be4815
      Joanne Hugé authored
      Some phones with Android 12+ disconnects from
      5G networks which don't support IMS. Therefore
      we add minimal IMS support in this commit (even
      though we don't actually need it's features).
      
      Only Amarisoft >= 2024-05-02 support launching
      lteims without root privilege, so if Amarisoft
      version is older IMS is disabled and we inform
      the user so in the connection parameters.
      
      For this to work, SIM cards config needs to be
      modified, impu and impi must be for instance:
      impu: 001010000001312,
      impi: 001010000001312@ims.mnc001.mcc001.3gppnetwork.org
      18be4815
  2. 30 May, 2024 1 commit
  3. 28 May, 2024 1 commit
    • Léo-Paul Géneau's avatar
      component/gcc: enable default PIE · f185af94
      Léo-Paul Géneau authored
      See merge request !1587
      
      Revert eb1b1a41 to avoid the use of
      `fPIC` flag as it is a "contagious" build option.
      
      To not face the build error "relocation R_X86_64_32 against
      .rodata.str1.8 can not be used when making a shared object; recompile
      with -fPIC" while building a shared library without fPIC flag, `gcc` is
      compiled with `-enable-default-pie` flag (which is a compilation option
      used for `gcc` binaries provided by Debian by example, see `gcc -v`).
      f185af94
  4. 27 May, 2024 2 commits
  5. 26 May, 2024 3 commits
  6. 25 May, 2024 9 commits
  7. 24 May, 2024 11 commits
  8. 23 May, 2024 1 commit
    • Kirill Smelkov's avatar
      stack/slapos: v↑ setuptools-dso 2.9 -> 2.10 · 5eed3c4b
      Kirill Smelkov authored
      With newer setuptools that is coming via !1550 (44.1.1 -> 67.8.0)
      we will need a fix from setuptools-dso 2.10 to handle `python setup develop` well:
      
      Previously with setutools-dso 2.9 and setuptools 67.8.0 built shared libraries were not
      copied back into the working tree upon develop install which made anything
      using pygolang to fail as e.g.
      
          $ ../bin/gpython
          Traceback (most recent call last):
            File ".../../bin/gpython", line 20, in <module>
              sys.exit(gpython.main())
            File ".../pygolang/gpython/__init__.py", line 456, in main
              pymain(argv, init)
            File ".../pygolang/gpython/__init__.py", line 223, in pymain
              init()
            File ".../pygolang/gpython/__init__.py", line 447, in init
              import golang
            File ".../pygolang/golang/__init__.py", line 41, in <module>
              from golang._gopath import gimport  # make gimport available from golang
            File ".../pygolang/golang/_gopath.py", line 65, in <module>
              from golang import sync
            File ".../pygolang/golang/sync.py", line 36, in <module>
              from golang._sync import \
          ImportError: liblibgolang.so.0.1: cannot open shared object file: No such file or directory
      
      See https://github.com/mdavidsaver/setuptools_dso/pull/29#issuecomment-1745790761
      and https://github.com/mdavidsaver/setuptools_dso/commit/2fdf75f2 for details.
      
      P.S. NOTE that changing version of a setup-egg required egg currently does
      _not_ force a rebuild. In other words pushing this change into testnodes won't
      make pygolang t o be rebuilt at all. I think this is simply a bug in
      slapos.buildout to fix.
      
      /reported-by @xavier_thompson
      /cc @jerome, @tomo, @kazuhiko
      /reviewed-on !1585
      5eed3c4b
  9. 22 May, 2024 2 commits
  10. 21 May, 2024 1 commit
  11. 20 May, 2024 8 commits