1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • Re: Package libllvm12:i386 does not exists on Debian ?

    From [email protected]@21:1/5 to Charles Curley on Sun Jun 16 18:10:01 2024
    On Sun, Jun 16, 2024 at 09:50:45AM -0600, Charles Curley wrote:

    [...]

    If you are on amd64 and want i386 packages, you must first enable the
    i386 packages. I'll let you search for the appropriate instructions.

    To me, that seems the most promising avenue.

    See dpkg --add-architecture to "add" another architecture to
    your package sources.

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZm8M1AAKCRAFyCz1etHa Rv8OAJ4xZ443776rBuHqb20MZFr34TTM/wCeLovn+Dk9CpExaJ4BpBCIQp4pRTU=
    =sSBW
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Charles Curley@21:1/5 to Mario Marietto on Sun Jun 16 18:00:01 2024
    On Sun, 16 Jun 2024 15:41:59 +0200
    Mario Marietto <[email protected]> wrote:

    I'm trying to compile wine-tkg from this repo :

    https://github.com/Frogging-Family/wine-tkg-git

    This is what I did,according with the short tutorial :

    root@debian-now:/home/marietto/Scaricati/wine-tkg-git/wine-tkg-git# ./non-makepkg-build.sh

    Installing package: libllvm12:i386 | Using apt
    E: Can't find package libllvm12:i386
    WARNING: Failed to install package: libllvm12:i386
    Installing apt-smart | Using pip
    error: externally-managed-environment
    × This environment is externally managed
    ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to
    install.

    Things you haven't told us:

    * Which version of Debian you are using. I'm going to assume Bookworm
    (12).

    * Whether you are running on i386 or amd64 or something completely
    different. I'm going to assume amd64.

    I have security concerns about build processes that just up and try to
    install packages for you. That sets off my paranoia alarms.

    If you are on amd64 and want i386 packages, you must first enable the
    i386 packages. I'll let you search for the appropriate instructions.

    As for why you aren't getting libllvm12 (of any architecture), that is
    likely because it isn't available in Bookworm. Strip off the version
    number, and search on that. I get:

    charles@issola:~$ apt-cache search libllvm
    libllvm-ocaml-dev - Low-Level Virtual Machine (LLVM), bindings for OCaml libllvm-13-ocaml-dev - Modular compiler and toolchain technologies, OCaml bindings
    libllvm13 - Modular compiler and toolchain technologies, runtime library libllvm-14-ocaml-dev - Modular compiler and toolchain technologies, OCaml bindings
    libllvm14 - Modular compiler and toolchain technologies, runtime library libllvm-15-ocaml-dev - Modular compiler and toolchain technologies, OCaml bindings
    libllvm15 - Modular compiler and toolchain technologies, runtime library libllvm-16-ocaml-dev - Modular compiler and toolchain technologies, OCaml bindings
    libllvm16 - Modular compiler and toolchain technologies, runtime library libllvmspirvlib-14-dev - bi-directional translator for LLVM/SPIRV -- development files
    libllvmspirvlib14 - bi-directional translator for LLVM/SPIRV -- shared library libllvmspirvlib-15-dev - bi-directional translator for LLVM/SPIRV -- development files
    libllvmspirvlib15 - bi-directional translator for LLVM/SPIRV -- shared library charles@issola:~$

    So your program appears to want a version of libllvm that has been
    dropped from bookworm. You should probably take that up with the
    developers of the program.



    --
    Does anybody read signatures any more?

    https://charlescurley.com
    https://charlescurley.com/blog/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From The Wanderer@21:1/5 to Hans on Sun Jun 16 18:50:01 2024
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
    On 2024-06-16 at 12:18, Hans wrote:

    I am wondering, why aptitude is showing me (incorrectlly?)
    libllvm*:i386 and apt-get not.

    I have no i386 entry in sources.list, but where does aptitude get its information?

    AFAIK, /etc/sources.list does not record architectures; it only records mirrors, which may have one architecture on them or may have multiple.

    In order to see whether or not you have 'i386' available as an enabled architecture, you can run:

    $ dpkg --print-foreign-architectures

    (That's assuming it isn't your native architecture, which since you
    suggest that it might be incorrect I'm assuming it isn't.)

    apt-cache search libllvm | grep i386

    'apt-cache search' does not report architecture qualifiers for packages.

    In comparison, you can run:

    $ apt-cache policy packagename packagename:i386

    and you should see that it shows you available-version and
    installed-version information for both architectures for that package.

    aptitude search libllvm | grep i386

    <snip>

    What did I miss?

    A difference in the default information displayed by the tools.

    --
    The Wanderer

    The reasonable man adapts himself to the world; the unreasonable one
    persists in trying to adapt the world to himself. Therefore all
    progress depends on the unreasonable man. -- George Bernard Shaw


    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEEJCOqsZEc2qVC44pUBKk1jTQoMmsFAmZvFLIACgkQBKk1jTQo MmsS3w//W8VXccfe6+ArKEs+UQKEFGoLMUKnnl5elTnNRbgUyoIA40A+rYo29n1Y XFveao4BEQzMEx0xRQPsrp5AylNNNJ0iP5bmDxo9uOva63k9N8kXenFye0cIUsPT PXmOp9FEXviprLr0M1tnDJdVBHw8iWYQs1STg8ZEIqeiC6NwoBQUKhu+Q/tOwNzH M2poI1RITEtDZL1HdLD8KVeOZSKhJFmVpa3ZXm0fs9Nco8/EYFfIcYt6NuZ5/jUB xetlO1UtZdiUORELMiSz2esP8whI0PWkMclTufgoeqZldScfrFAZsAHZ6fA10wuy IhEFaS58jo85Nz5JO6z1uCbZTg3qIKTFCycBM7az2lyp+JZhI/zN2zFYOAjHr/93 Yqve015Lx+3d2kk6YlVF5KO+29/27s9jHEpAAyEQ/Adqb6/ulfyru8KiqVZEuUlg s7HIup9PuirHYosUIbXr69WKD7/8F2iHkZij5pVtcNXb39RxuOH75YicL9Lyrxhp Ma5eHVhZEVPtQzvi4ek1BQw3VQa7w8k3zFJo7yFVsAR3bcYl6ZW4UTEueyA+aTs5 i680fheLGkhU9bAKuC/k5CE1XqjLXfAkMAAa6drtT4SLtUqoqNIhCwiAGck6JbUv wCf2OzKUQcYAWnFRwzQR7uj0eScG
  • From [email protected]@21:1/5 to The Wanderer on Sun Jun 16 19:30:01 2024
    On Sun, Jun 16, 2024 at 12:37:06PM -0400, The Wanderer wrote:
    On 2024-06-16 at 12:18, Hans wrote:

    I am wondering, why aptitude is showing me (incorrectlly?)
    libllvm*:i386 and apt-get not.

    I have no i386 entry in sources.list, but where does aptitude get its information?

    AFAIK, /etc/sources.list does not record architectures; it only records mirrors, which may have one architecture on them or may have multiple.

    In order to see whether or not you have 'i386' available as an enabled architecture, you can run:

    $ dpkg --print-foreign-architectures

    Indeed, multi-arch is a dpkg thing. The list of current architectures
    is kept in /var/lib/dpkg/arch [1]

    Cheers
    --
    tomás

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZm8e0gAKCRAFyCz1etHa Ro5xAJ0du6X7h5InHY5P5vkgHnSrLuQKRgCfRr3WAPPAJDfAzbtI/u+Rh0nWJ+4=
    =mKyW
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)