Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

1 votes
1 answers
75 views
How do I build a statically linked copy of xz-utils?
I'm trying to build a statically linked copy of xz-utils, such that the `xz` do not have dependencies on libc. I tried the usual way, which is to set LDFLAGS=-static, and works for most other packages out there. In the case of xz-utils, however, the binary is built successfully but it is statically...
I'm trying to build a statically linked copy of xz-utils, such that the xz do not have dependencies on libc. I tried the usual way, which is to set LDFLAGS=-static, and works for most other packages out there. In the case of xz-utils, however, the binary is built successfully but it is statically linked, as can be seen here.
$ docker run --rm -it -v $PWD/downloads:/downloads --platform linux/amd64 alpine:3
/ # cd ~
~ # apk add build-base clang
...
~ # tar -xf /downloads/xz-5.8.1.tar.gz 
~ # PREFIX=/opt/xz-5.8.1
~ # cd xz-5.8.1/
~ # export CC=clang 
~ # export LDFLAGS=-static
~/xz-5.8.1 # LDFLAGS=-static CC=clang ./configure --prefix=$PREFIX --disable-nls --disable-doc --disable-microlzma
[See https://pastebin.com/Cj6ZX9sC] 
~/xz-5.8.1 # make -j4
[See https://pastebin.com/79wmN4zS] 
~/xz-5.8.1 # make install
[See https://pastebin.com/iCpCG3hQ] 
~/xz-5.8.1 # ldd /opt/xz-5.8.1/bin/xz
        /lib/ld-musl-x86_64.so.1 (0x7fe94c28b000)
        libc.musl-x86_64.so.1 => /lib/ld-musl-x86_64.so.1 (0x7fe94c28b000)
How do I solve this?
rs3 (11 rep)
Apr 6, 2025, 02:32 PM • Last activity: Apr 6, 2025, 04:18 PM
3 votes
2 answers
871 views
Problem with installing Clang: undefined symbol: LLVMInitializeMipsAsmParser
I'm new to Linux environment. Few days ago I've installed Fedora on my laptop. I want to complie some C++ source code but having trouble with Clang. First, after installing it with *yum* I see an error (whenever I call `clang` in the console): clang: symbol lookup error: clang: undefinied symbol: LL...
I'm new to Linux environment. Few days ago I've installed Fedora on my laptop. I want to complie some C++ source code but having trouble with Clang. First, after installing it with *yum* I see an error (whenever I call clang in the console): clang: symbol lookup error: clang: undefinied symbol: LLVMInitializeMipsAsmParser After trying different methods I gave up on installing Clang and wanted to stick to g++. OK. but today I wanted to install some IDE. Decided to go with CodeLite and... whenever I want to open CodeLite it gives me this error: /lib64/libclang.so.3.8: undefined symbol: LLVMInitializeMipsAsmParser Seems like CodeLite is installing Clang by default and I ending up with the same error... To be honest I've tried to build LLVM from source but that didn't help (I guess Clang has to know somehow where to look for those symbols and I don't know how to tell it) and I don't have enough disc space to build LLVM & Clang at the same time (it takes 20+ GB...) following instructions from here: http://llvm.org/docs/GettingStarted.html#getting-started-quickly-a-summary
pmakal (31 rep)
Mar 6, 2017, 10:32 PM • Last activity: Feb 24, 2025, 07:41 PM
1 votes
1 answers
7226 views
How to install the latest stable Clang on Fedora?
I'm considering switching to Fedora, but the latest stable Fedora (36) only ships Clang 14, while the latest release is Clang 15. Is there any way to get up-to-date binaries, without switching to the beta version of Fedora? I found https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snap...
I'm considering switching to Fedora, but the latest stable Fedora (36) only ships Clang 14, while the latest release is Clang 15. Is there any way to get up-to-date binaries, without switching to the beta version of Fedora? I found https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm-snapshots/ , but they only produce trunk builds, not the stable releases.
HolyBlackCat (170 rep)
Oct 8, 2022, 03:09 PM • Last activity: Jan 31, 2025, 03:30 AM
0 votes
0 answers
39 views
Can clang-17-dev be installed on debian bullseye?
I want to use cl-bindgen and it depends on `libclang-17.so` I am on a x86_64 debian bullseye machine. After several attempts, I seem unable to install `clang-17-dev`, which supposedly has `libclang-17.so`. Any tips on how I can install it? I tried adding the debian sid unstable branch to my apt conf...
I want to use cl-bindgen and it depends on libclang-17.so I am on a x86_64 debian bullseye machine. After several attempts, I seem unable to install clang-17-dev, which supposedly has libclang-17.so. Any tips on how I can install it? I tried adding the debian sid unstable branch to my apt configuration but it still did not work.
BitTickler (131 rep)
Dec 29, 2024, 10:39 PM
2 votes
0 answers
109 views
when is the environ symbol defined in the executable?
If I compile a simple test program, I get environment symbols defined (and exported) in the executable itself: ``` root@4ef8c4a55769:/# clang --version Debian clang version 11.0.1-2 Target: aarch64-unknown-linux-gnu Thread model: posix InstalledDir: /usr/bin root@4ef8c4a55769:/# cat /tmp/a.c #includ...
If I compile a simple test program, I get environment symbols defined (and exported) in the executable itself:
root@4ef8c4a55769:/# clang --version
Debian clang version 11.0.1-2
Target: aarch64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
root@4ef8c4a55769:/# cat /tmp/a.c
#include 

extern const char *const  * __environ;

int main() {
    if (!__environ) {
        return 1;
    }
    for (__auto_type p = __environ; *p; p++) {
        puts(*p);
    }
    return 0;
}
root@4ef8c4a55769:/# clang /tmp/a.c
root@4ef8c4a55769:/# ./a.out 
_=./a.out
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
SHLVL=1
TERM=xterm
HOME=/root
PWD=/
HOSTNAME=4ef8c4a55769
root@4ef8c4a55769:/# readelf --wide --dyn-syms a.out | grep environ
     5: 0000000000411030     8 OBJECT  WEAK   DEFAULT   25 _environ@GLIBC_2.17 (2)
     6: 0000000000411030     8 OBJECT  WEAK   DEFAULT   25 environ@GLIBC_2.17 (2)
     7: 0000000000411030     8 OBJECT  GLOBAL DEFAULT   25 __environ@GLIBC_2.17 (2)
this is despite the fact that glibc itself defines these:
root@4ef8c4a55769:/# readelf --dyn-syms --wide /lib/aarch64-linux-gnu/libc.so.6 | grep environ
   296: 0000000000172658     8 OBJECT  WEAK   DEFAULT   31 _environ@@GLIBC_2.17
  1007: 0000000000172658     8 OBJECT  WEAK   DEFAULT   31 environ@@GLIBC_2.17
  1334: 0000000000172658     8 OBJECT  GLOBAL DEFAULT   31 __environ@@GLIBC_2.17
however, I have executables where this is imported (including one program I compiled myself, though the same program compiled with the same compiler but on amd64 still defines environ):
root@4ef8c4a55769:/# readelf --wide --dyn-syms /bin/bash | grep environ
   123: 0000000000000000     0 OBJECT  WEAK   DEFAULT  UND _environ@GLIBC_2.17 (2)
   185: 0000000000000000     0 OBJECT  GLOBAL DEFAULT  UND __environ@GLIBC_2.17 (2)
   191: 0000000000000000     0 OBJECT  GLOBAL DEFAULT  UND environ@GLIBC_2.17 (2)
   ...
To have it imported is my desired behavior. The reason is that I get incorrect runtime linking (as seen with LD_DEBUG) when there are two __environ symbols: libc binds to the executable, but the executable and later loaded dynamic libraries bind to libc. This results in the __environ from the executable being populated, but not the one defined in libc. My question is: what determines this behavior, and how can I force __environ imported? EDIT: Interestingly, if I compile with GCC the symbols don't get defined (though on amd64 they are still defined):
root@4ef8c4a55769:/# gcc --version
gcc (Debian 10.2.1-6) 10.2.1 20210110
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
The link line for gcc is:
/usr/lib/gcc/aarch64-linux-gnu/10/collect2 -plugin /usr/lib/gcc/aarch64-linux-gnu/10/liblto_plugin.so -plugin-opt=/usr/lib/gcc/aarch64-linux-gnu/10/lto-wrapper -plugin-opt=-fresolution=/tmp/ccnbGUtW.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id --eh-frame-hdr --hash-style=gnu --as-needed -dynamic-linker /lib/ld-linux-aarch64.so.1 -X -EL -maarch64linux --fix-cortex-a53-843419 -pie /usr/lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu/Scrt1.o /usr/lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu/crti.o /usr/lib/gcc/aarch64-linux-gnu/10/crtbeginS.o -L/usr/lib/gcc/aarch64-linux-gnu/10 -L/usr/lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu -L/usr/lib/gcc/aarch64-linux-gnu/10/../../../../lib -L/lib/aarch64-linux-gnu -L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/aarch64-linux-gnu/10/../../.. /tmp/cccSV4NT.o -lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state /usr/lib/gcc/aarch64-linux-gnu/10/crtendS.o /usr/lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu/crtn.o
and for clang:
"/usr/bin/ld" -EL --hash-style=both --build-id --eh-frame-hdr -m aarch64linux -dynamic-linker /lib/ld-linux-aarch64.so.1 -o a.out /usr/bin/../lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu/crt1.o /usr/bin/../lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu/crti.o /usr/bin/../lib/gcc/aarch64-linux-gnu/10/crtbegin.o -L/usr/bin/../lib/gcc/aarch64-linux-gnu/10 -L/usr/bin/../lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu -L/lib/aarch64-linux-gnu -L/usr/lib/aarch64-linux-gnu -L/usr/bin/../lib/gcc/aarch64-linux-gnu/10/../../.. -L/usr/lib/llvm-11/bin/../lib -L/lib -L/usr/lib /tmp/a-06a7fe.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/bin/../lib/gcc/aarch64-linux-gnu/10/crtend.o /usr/bin/../lib/gcc/aarch64-linux-gnu/10/../../../aarch64-linux-gnu/crtn.o
Artefacto (255 rep)
Jul 10, 2024, 11:46 PM • Last activity: Jul 10, 2024, 11:53 PM
3 votes
1 answers
2802 views
Print clang include path and store in file
I'm writing a program that needs to pull in the clang include paths. Thanks to [Dump include paths from g++][1] I'm half-way there. The command I'm using is: clang++ -E -x c++ - -v stdout.txt clang++ -E -x c++ - -v stderr.txt So where is the output being redirected to and what command do I need to e...
I'm writing a program that needs to pull in the clang include paths. Thanks to Dump include paths from g++ I'm half-way there. The command I'm using is: clang++ -E -x c++ - -v stdout.txt clang++ -E -x c++ - -v stderr.txt So where is the output being redirected to and what command do I need to execute to properly store off the information that is printed to console?
Max (131 rep)
Jan 15, 2020, 07:23 PM • Last activity: Apr 19, 2024, 08:49 PM
0 votes
1 answers
345 views
How to add pkgs.org and other mirrors in centOS 8?
``` https://centos.pkgs.org/8-stream/centos-appstream-x86_64/ http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/ ``` I am new to centOS. I want to add these two repositories so that whenver I use yum install I get the latest packages from them. For example I want to install clang...
https://centos.pkgs.org/8-stream/centos-appstream-x86_64/ 
http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/ 
I am new to centOS. I want to add these two repositories so that whenver I use yum install I get the latest packages from them. For example I want to install clang 17. Currently when I input yum install clang It shows clang 12 which is pretty outdated. I want the result like When I input sudo yum install clang it shows the clang version 17
Zeshan Ahmed Nobin (111 rep)
Apr 16, 2024, 06:23 AM • Last activity: Apr 16, 2024, 05:57 PM
0 votes
0 answers
98 views
Unable to build a cpp program on AIX with gcc fsanitize address
I'm trying to build a cpp program on AIX 7.2 using gcc with address sanitizer (`-fsanitize=address`) but this errors out with: ``` cc1plus: warning: '-fsanitize=address' not supported for this target collect2: fatal error: library libasan not found compilation terminated. ``` I thought maybe the com...
I'm trying to build a cpp program on AIX 7.2 using gcc with address sanitizer (-fsanitize=address) but this errors out with:
cc1plus: warning: '-fsanitize=address' not supported for this target
collect2: fatal error: library libasan not found
compilation terminated.
I thought maybe the compilation will succeed if I have the libasan shared library. So I tried building llvm from source but running into the same issue with that:
> export CC=gcc; export CXX=g++;
> cmake -DLLVM_ENABLE_PROJECTS=clang -DLLVM_ENABLE_RUNTIMES=compiler-rt -DCMAKE_INSTALL_PREFIX=/llvm_install -DLLVM_USE_SANITIZER=Address -DCMAKE_BUILD_TYPE=Debug -DLLVM_TARGETS_TO_BUILD="PowerPC" -G "Unix Makefiles" /llvm-project/llvm
Consolidate compiler generated dependencies of target LLVMDemangle
[  0%] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
cc1plus: error: '-fsanitize=address' not supported for this target [-Werror]
cc1plus: all warnings being treated as errors
My environment:
gcc version 10.3.0
cmake version 3.20.0
AIX 7.2
**Questions:** 1. Does gcc not support fsanitize=address on AIX? 2. Has someone successfully built a cpp program with address sanitizer on AIX? If so, can you please share the steps. 3. Do I need to use xlc ? Is there no way to make this work with gcc? Apologies if this it not the right forum to ask AIX queries.
Sanchit Gupta (1 rep)
Jan 15, 2024, 05:59 AM
0 votes
0 answers
99 views
configure: error: C compiler cannot create executables ERROR on FreeBSD 14.0-RELEASE
I'm not able to install sudo on my FreeBSD 14.0-RELEASE-p3 amd64 marietto:/usr/ports/security/sudo # make ===> License sudo accepted by the user ===> sudo-1.9.15p4 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by sudo-1.9.15p4 for building ===> Extracting for sudo...
I'm not able to install sudo on my FreeBSD 14.0-RELEASE-p3 amd64 marietto:/usr/ports/security/sudo # make ===> License sudo accepted by the user ===> sudo-1.9.15p4 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by sudo-1.9.15p4 for building ===> Extracting for sudo-1.9.15p4 => SHA256 Checksum OK for sudo-1.9.15p4.tar.gz. ===> Patching for sudo-1.9.15p4 ===> Applying FreeBSD patches for sudo-1.9.15p4 from /usr/ports/security/sudo/files ===> sudo-1.9.15p4 depends on package: pkgconf>=1.3.0_1 - found ===> sudo-1.9.15p4 depends on package: gettext-runtime>=0.22_1 - found ===> sudo-1.9.15p4 depends on executable: msgfmt - found ===> sudo-1.9.15p4 depends on file: /usr/local/lib/libcrypto.so.12 - found ===> sudo-1.9.15p4 depends on shared library: libintl.so - found (/usr/local/lib/libintl.so) ===> Configuring for sudo-1.9.15p4 configure: loading site script /usr/ports/Templates/config.site checking for gcc... cc checking whether the C compiler works... no configure: error: in '/usr/ports/security/sudo/work/sudo-1.9.15p4': configure: error: C compiler cannot create executables See 'config.log' for more details ===> Script "configure" failed unexpectedly. Please report the problem to garga@FreeBSD.org [maintainer] and attach the "/usr/ports/security/sudo/work/sudo-1.9.15p4/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make: stopped in /usr/ports/security/sudo *** Error code 1 Stop. make: stopped in /usr/ports/security/sudo More informations are located here : /usr/local/sbin/pkg-static info -g -Ea = https://pastebin.ubuntu.com/p/3fCY3hFRCG/ /usr/ports/security/sudo/work/sudo-1.9.15p4/config.log = https://pastebin.ubuntu.com/p/PK2QxNHwkk/ I suspect some misconfiguration on the gcc / cc / clang compiler. I expect that sudo won't be installed telling that it has been already installed from packages,but the error is different.
mister_smith (1 rep)
Dec 31, 2023, 04:48 PM
0 votes
0 answers
365 views
ld error with clangs when compiling vdso
i am trying to compile a kernel but it always return this error: ``` LD arch/arm64/kernel/vdso/built-in.o ld.lld: error: cannot find linker script -r make[2]: *** [scripts/Makefile.build:507: arch/arm64/kernel/vdso/built-in.o] Error 1 make[1]: *** [scripts/Makefile.build:647: arch/arm64/kernel/vdso]...
i am trying to compile a kernel but it always return this error:
LD      arch/arm64/kernel/vdso/built-in.o
ld.lld: error: cannot find linker script -r
make: *** [scripts/Makefile.build:507: arch/arm64/kernel/vdso/built-in.o] Error 1
make: *** [scripts/Makefile.build:647: arch/arm64/kernel/vdso] Error 2
make: *** [Makefile:1239: arch/arm64/kernel] Error 2
i have examined the sources, scripts and Makefiles from vdso but no luck. can anyone point me how and where to look into this matter, or how to show more details about this please? regards edit: i am trying to build an android kernel with llvm for the first time on my ubuntu 20.04, which i believe i have setup clang17 & gcc probably. but it produced the same error even compiled with gcc here is the config settings:
CLANG_HOME=/usr/lib/llvm-17
export PATH=$CLANG_HOME/bin:$CLANG_HOME/lib:${PATH}
export CLANG_TRIPLE=/usr/bin/aarch64-linux-gnu-
export CROSS_COMPILE=/usr/bin/aarch64-linux-gnu-
export CROSS_COMPILE_ARM32=/opt1/android/toolchain/clang/proton-clang-v13.0.0/arm-linux-gnueabi/bin/arm-linux-gnueabi-
export CC=$CLANG_HOME/bin/clang
export REAL_CC=$CLANG_HOME/bin/clang
export LD=$CLANG_HOME/bin/ld.lld
export AR=$CLANG_HOME/bin/llvm-ar
export NM=$CLANG_HOME/bin/llvm-nm
export OBJCOPY=$CLANG_HOME/bin/llvm-objcopy
export OBJDUMP=$CLANG_HOME/bin/llvm-objdump
export READELF=$CLANG_HOME/bin/llvm-readelf
export STRIP=$CLANG_HOME/bin/llvm-strip
export LLVM=1 && export LLVM_IAS=1
export KALLSYMS_EXTRA_PASS=1
export ARCH=arm64 && export SUBARCH=arm64
errors with make -j1 -V1
make -f ./scripts/Makefile.build obj=arch/arm64/kernel/vdso
  /usr/lib/llvm-17/bin/llvm-objcopy -S  arch/arm64/kernel/vdso/vdso.so.dbg arch/arm64/kernel/vdso/vdso.so
  /usr/lib/llvm-17/bin/clang -Wp,-MD,arch/arm64/kernel/vdso/.vdso.o.d  -nostdinc -isystem /usr/lib/llvm-17/lib/clang/17/include -I./arch/arm64/include -I./arch/arm64/include/generated/uapi -I./arch/arm64/include/generated  -I./include -I./drivers/kernelsu/include -I./arch/arm64/include/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -Qunused-arguments -mlittle-endian -Qunused-arguments -D__ASSEMBLY__ --target=aarch64-linux-gnu -DCC_USE_CLANG --prefix=/usr/bin/aarch64-linux-gnu-
--gcc-toolchain=/usr -Werror=unknown-warning-option -fno-PIE -DCONFIG_AS_LSE=1 -DCONFIG_VDSO32=1   -c -o arch/arm64/kernel/vdso/vdso.o arch/arm64/kernel/vdso/vdso.S
   /usr/lib/llvm-17/bin/ld.lld   -EL  -maarch64elf -O3 -shared -nostdlib -soname=linux-vdso.so.1 --hash-style=sysv --build-id -n -T
-r -o arch/arm64/kernel/vdso/built-in.o arch/arm64/kernel/vdso/vdso.o
ld.lld: error: cannot find linker script -r
make: *** [scripts/Makefile.build:507: arch/arm64/kernel/vdso/built-in.o] Error 1
make: *** [scripts/Makefile.build:647: arch/arm64/kernel/vdso] Error 2
make: *** [Makefile:1239: arch/arm64/kernel] Error 2
edit2: tried with different clang but still having problems when compiling vdso things. most common errors as mentioned above - cannot find linker script, thus built.o was not compiled successfully
xxjoe (11 rep)
Sep 21, 2023, 12:54 PM • Last activity: Oct 23, 2023, 10:00 AM
1 votes
0 answers
703 views
How to install LLVM-14 on Ubuntu?
I have installed LLVM-14 on Ubuntu manually. Everything seems to work fine except `ld` during the compilation of `cargo-bpf` in Rust cargo. ``` = note: /usr/bin/ld: cannot find -lLLVM-14 collect2: error: ld returned 1 exit status error: could not compile `cargo-bpf` (bin "cargo-bpf") due to previous...
I have installed LLVM-14 on Ubuntu manually. Everything seems to work fine except ld during the compilation of cargo-bpf in Rust cargo.
= note: /usr/bin/ld: cannot find -lLLVM-14
          collect2: error: ld returned 1 exit status
          

error: could not compile cargo-bpf (bin "cargo-bpf") due to previous error
Output of llvm-config --version
root@ip-172-31-0-42:/opt/llvm/cs-fw# llvm-config --version
14.0.0
LLVM path: /opt/llvm/clang+llvm-14.0.0-x86_64-linux-gnu-ubuntu-18.04
HyperX Pro (111 rep)
Aug 14, 2023, 09:18 PM • Last activity: Aug 14, 2023, 09:19 PM
1 votes
1 answers
282 views
OpenBSD: npm install sodium-native, interpret error messages
I am attempting to install [sodium native][1] as an npm package on OpenBSD 7.3 amd64. *Aside: As a dependency of [Hypercore, Hyperbee and Corestore][2].* This needs [node-gyp][3]. Following [this][4], I set the C and C++ compilers to clang: export CC=clang export CXX=clang++ I created a directory `e...
I am attempting to install sodium native as an npm package on OpenBSD 7.3 amd64. *Aside: As a dependency of Hypercore, Hyperbee and Corestore .* This needs node-gyp . Following this , I set the C and C++ compilers to clang: export CC=clang export CXX=clang++ I created a directory example and, for development/debugging only, I set the permissions via chmod 777. I then used npm init to create an empty package.json file. On running npm install sodium-native, I get the following error logs: 395 info run sodium-native@4.0.1 install node_modules/sodium-native node-gyp-build 396 info run sodium-native@4.0.1 install { code: 1, signal: null } 397 timing reify:rollback:createSparse Completed in 4183ms 398 timing reify:rollback:retireShallow Completed in 0ms 399 timing command:install Completed in 31258ms 400 verbose stack Error: command failed 400 verbose stack at ChildProcess. (/usr/local/lib/node_modules/@npmcli/promise-spawn/lib/index.js:53:27) 400 verbose stack at ChildProcess.emit (node:events:513:28) 400 verbose stack at maybeClose (node:internal/child_process:1091:16) 400 verbose stack at Socket. (node:internal/child_process:449:11) 400 verbose stack at Socket.emit (node:events:513:28) 400 verbose stack at Pipe. (node:net:322:12) 401 verbose pkgid sodium-native@4.0.1 402 verbose cwd /example 403 verbose OpenBSD 7.3 404 verbose node v18.15.0 405 verbose npm v9.5.0 406 error code 1 407 error path /example/node_modules/sodium-native 408 error command failed 409 error command sh -c node-gyp-build 410 error gyp info it worked if it ends with ok 410 error gyp info using node-gyp@9.3.1 410 error gyp info using node@18.15.0 | openbsd | x64 410 error gyp info find Python using Python version 3.10.11 found at "/usr/local/bin/python3" 410 error gyp info spawn /usr/local/bin/python3 410 error gyp info spawn args [ 410 error gyp info spawn args '/usr/local/lib/node_modules/node-gyp/gyp/gyp_main.py', 410 error gyp info spawn args 'binding.gyp', 410 error gyp info spawn args '-f', 410 error gyp info spawn args 'make', 410 error gyp info spawn args '-I', 410 error gyp info spawn args '/example/node_modules/sodium-native/build/config.gypi', 410 error gyp info spawn args '-I', 410 error gyp info spawn args '/usr/local/lib/node_modules/node-gyp/addon.gypi', 410 error gyp info spawn args '-I', 410 error gyp info spawn args '/root/.cache/node-gyp/18.15.0/include/node/common.gypi', 410 error gyp info spawn args '-Dlibrary=shared_library', 410 error gyp info spawn args '-Dvisibility=default', 410 error gyp info spawn args '-Dnode_root_dir=/root/.cache/node-gyp/18.15.0', 410 error gyp info spawn args '-Dnode_gyp_dir=/usr/local/lib/node_modules/node-gyp', 410 error gyp info spawn args '-Dnode_lib_file=/root/.cache/node-gyp/18.15.0/<(target_arch)/node.lib', 410 error gyp info spawn args '-Dmodule_root_dir=/example/node_modules/sodium-native', 410 error gyp info spawn args '-Dnode_engine=v8', 410 error gyp info spawn args '--depth=.', 410 error gyp info spawn args '--no-parallel', 410 error gyp info spawn args '--generator-output', 410 error gyp info spawn args 'build', 410 error gyp info spawn args '-Goutput_dir=.' 410 error gyp info spawn args ] 410 error node:events:491 410 error throw er; // Unhandled 'error' event 410 error ^ 410 error 410 error Error: write EPIPE 410 error at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16) 410 error Emitted 'error' event on Socket instance at: 410 error at Socket.onerror (node:internal/streams/readable:785:14) 410 error at Socket.emit (node:events:513:28) 410 error at emitErrorNT (node:internal/streams/destroy:151:8) 410 error at emitErrorCloseNT (node:internal/streams/destroy:116:3) 410 error at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { 410 error errno: -32, 410 error code: 'EPIPE', 410 error syscall: 'write' 410 error } 410 error 410 error Node.js v18.15.0 410 error gyp: Call to 'node deps/bin.js --print-include' returned exit status 1 while in binding.gyp. while trying to load binding.gyp 410 error gyp ERR! configure error 410 error gyp ERR! stack Error: gyp failed with exit code: 1 410 error gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/node-gyp/lib/configure.js:325:16) 410 error gyp ERR! stack at ChildProcess.emit (node:events:513:28) 410 error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12) 410 error gyp ERR! System OpenBSD 7.3 410 error gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild" 410 error gyp ERR! cwd /example/node_modules/sodium-native 410 error gyp ERR! node -v v18.15.0 410 error gyp ERR! node-gyp -v v9.3.1 410 error gyp ERR! not ok 411 verbose exit 1 412 timing npm Completed in 31440ms 413 verbose unfinished npm timer reify 1683196282136 414 verbose unfinished npm timer reify:build 1683196305333 415 verbose unfinished npm timer build 1683196305334 416 verbose unfinished npm timer build:deps 1683196305334 417 verbose unfinished npm timer build:run:install 1683196305349 418 verbose unfinished npm timer build:run:install:node_modules/sodium-native 1683196307572 419 verbose code 1 420 error A complete log of this run can be found in: 420 error /root/.npm/_logs/2023-05-04T10_31_22_018Z-debug-0.log The node_modules directory did not get created. I am unsure how to interpret this. It's not clear to me whether its a permissions problem, a compiler toolchain problem, or something else. What might be going wrong here? What next steps could I take? --- **EDIT:** Further investigation : The problem can be more directly recreated like so: pkg_add git git clone --branch v3.3.0 https://github.com/sodium-friends/sodium-native pkg_add node cd s* node deps/bin.js --print-include --print-lib --print-arch Using console.logs in deps/bin.js narrows down the problem a socket created on a process object by the run function , when passed 'tar' and 'xzv' arguments (after attempting to fetch libsodium from https://download.libsodium.org/libsodium/releases/libsodium-1.0.18.tar.gz); when it attempts to pipe between sockets . I saw this , and wonder if there is any reason that OpenBSD might prematurely close the socket? Possibly relevant links: https://stackoverflow.com/questions/39739626/what-is-node-gyp https://stackoverflow.com/questions/58436786/build-of-sodium-native-on-centos-cloud-is-failing https://stackoverflow.com/questions/39855232/npm-install-fails-with-node-gyp-build-error https://github.com/prebuild/node-gyp-build/issues/8 https://github.com/nodejs/node-gyp/issues/809 --- *Note: adapted and cross-posted here .*
Lee (549 rep)
May 4, 2023, 11:08 AM • Last activity: May 8, 2023, 06:33 PM
0 votes
1 answers
647 views
Kate Editor LSP Client: Any way to specify an "entry file" for compilation?
Goal: If I have two c files, A and B, and I don't plan to compile B into an object file, but rather include it directly in A, can clangd (or any other LSP service that works with Kate) show me only the errors in B that arise from compiling A directly? In other words, A is the "entry file" for compil...
Goal: If I have two c files, A and B, and I don't plan to compile B into an object file, but rather include it directly in A, can clangd (or any other LSP service that works with Kate) show me only the errors in B that arise from compiling A directly? In other words, A is the "entry file" for compilation errors in B. Please bare with the me on the snubbing of standard include practices. Simplest example: Let's say this is main.c: #include #include "test.c" int main() { test(); return 0; } and test.c is: void test() { printf("Hello world!\n"); } If I were to compile test.c into an object file, I would get the following errors: > clang -c test.c -o test test.c:2:5: warning: implicitly declaring library function 'printf' with type 'int (const char *, ...)' [-Wimplicit-function-declaration] printf("Hello world!\n"); ^ test.c:2:5: note: include the header or explicitly provide a declaration for 'printf' Kate's LSP Server will of course pick up on this and highlight "printf" in test.c for fixing. Now, let's say I have no plan to compile test.c separately. I only want to run: clang main.c Which will include test.c AFTER stdio is included in main.c, and thus compile without errors. Therefore the printf warning the LSP server shows me - while good for demonstrating test.c's compile-ability in isolation - will be irrelevant to how I ultimately compile the program. In this scenario, can I tell the LSP server to ONLY compile main.c (treat main.c as the "entry point" of compilation), and then have kate only highlight the errors in test.c that would arise from compiling main.c? In the concrete example, this would lead to NO errors being highlighted in test.c. I might also be snubbing the definition of "entry point", since it usually refers to runtime entry point, not certain compilation choices, but if there's a name for what I'm asking for, I'm not sure what it is.
Eagle Orion (1 rep)
Sep 24, 2022, 07:45 PM • Last activity: Feb 24, 2023, 01:29 PM
1 votes
0 answers
1982 views
unrecognized option '-EL'
I'm trying to build an android kernel. On every build I get a few errors: - /usr/bin/as: unrecognized option '-EL' clang-16: error: assembler command failed with exit code 1 (use -v to see invocation) - warning: field 'cgrp' with variable sized type 'struct cgroup' not at the end of a struct or clas...
I'm trying to build an android kernel. On every build I get a few errors: - /usr/bin/as: unrecognized option '-EL' clang-16: error: assembler command failed with exit code 1 (use -v to see invocation) - warning: field 'cgrp' with variable sized type 'struct cgroup' not at the end of a struct or class is a GNU extension [-Wgnu-variable-sized-type-not-at-end] struct group cgrp; - warning: unused function 'dump_workqueue' [-Wunused-function] static void dump_workqueue(void) {} Here are what I've tried so far 1. I tried different versions of clang, including proton-clang . 2. Tried different build methods, with and without a .sh script - basically followed the advice from YouTube build videos (here are some of them: one , two , three ). 3. Tried changing distribute linux. 4. Tried to change kernel build configuration. 5. At the end, I combined several options and results from this question , but unfortunately it didn't work for me. No more ideas and information on the Internet. Please help me how to solve this. I use clang-r475365b and gcc android-11.0.0_r48 My Kernel: https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/SM8250_R_11.0 My build.sh: #!/usr/bin/bash if [[ -d "out" ]] then cd out && make clean && make distclean && make mrproper && cd .. else mkdir -p out fi make O=out ARCH=arm64 vendor/bengal-perf_defconfig PATH="${HOME}/heh/Desktop/clang/bin:${HOME}/heh/Desktop/toolchains/bin${PATH}" \ LD_LIBRARY_PATH="${HOME}/heh/Desktop/clang/lib:${HOME}/heh/Desktop/toolchains/lib${PATH}" \ make O=out \ ARCH=arm64 \ SUBARCH=arm64 \ CROSS_COMPILE=aarch64-linux-android- \ CROSS_COMPILER=$PATH \ CLANG_TRIPLE=aarch64-linux-gnu- \ RANLIB=/home/heh/Desktop/clang/bin/llvm-ranlib \ CC='/home/heh/Desktop/clang/bin/clang -fintegrated-as' \ AR=/home/heh/Desktop/clang/bin/llvm-ar \ AS=/home/heh/Desktop/clang/bin/llvm-as \ NM=/home/heh/Desktop/clang/bin/llvm-nm \ OBJCOPY=/home/heh/Desktop/clang/bin/llvm-objcopy \ OBJDUMP=/home/heh/Desktop/clang/bin/llvm-objdump \ READELF=/home/heh/Desktop/clang/bin/llvm-readelf \ OBJSIZE=/home/heh/Desktop/clang/bin/llvm-size \ STRIP=/home/heh/Desktop/clang/bin/llvm-strip \ -j4 I took it from here , but the solution presented there did not help
JohnTit (11 rep)
Feb 11, 2023, 03:16 PM • Last activity: Feb 11, 2023, 11:21 PM
1 votes
0 answers
646 views
Termux Bash: ./ Permission Denied
I have a file `Test.cpp` that I compiled into `test` using `clang++`, but running it, I get the error in the title. I have tried using `chmod u+x test` and `chmod 775 test`, among other commands, but using `ls -l` shows that all files still only have read and write permissions, for example: `-rw-rw-...
I have a file Test.cpp that I compiled into test using clang++, but running it, I get the error in the title. I have tried using chmod u+x test and chmod 775 test, among other commands, but using ls -l shows that all files still only have read and write permissions, for example: -rw-rw---- 1 u0_a234 media_rw 516 Jan 15 11:58 Sample.cpp The -rw-rw---- is shown on all the files in the directory, even one that I created just now with nano hello.cpp, which also couldn't run once compiled Weirdly though, Test.py works when I run it with my installed python program. When I installed python, it looked like it automatically installed clang as well, based on the text it output and the fact that I can compile cpp files I'm still very new to bash/Linux stuff and I'm guessing that it has something to do with file permissions on Android, but if someone could shed some insight onto this I'd really appreciate it Edit: removed image, I was lazy and didn't read the rules regarding that, sorry
Sandman (11 rep)
Jan 15, 2023, 09:42 PM • Last activity: Jan 15, 2023, 11:29 PM
0 votes
1 answers
1583 views
Fail to install Clang-3.5 due to Clang-3.3
I am trying to install clang-3.5 on Linux Mint 17.2 (Cinnamon) and I dependency errors. Edit: here is the output of `apt-cache policy clang clang-3.5 clang-3.3`: clang: Installed: (none) Candidate: 1:3.4-0ubuntu1 Version table: 1:3.4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe a...
I am trying to install clang-3.5 on Linux Mint 17.2 (Cinnamon) and I dependency errors. Edit: here is the output of apt-cache policy clang clang-3.5 clang-3.3: clang: Installed: (none) Candidate: 1:3.4-0ubuntu1 Version table: 1:3.4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages clang-3.5: Installed: (none) Candidate: 1:3.5-4ubuntu2~trusty2 Version table: 1:3.5-4ubuntu2~trusty2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 1:3.5~svn201651-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages clang-3.3: Installed: (none) Candidate: 1:3.3-16ubuntu1 Version table: 1:3.3-16ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages And here is the output of sudo apt-get install clang-3.5: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: clang-3.5 : Breaks: clang-3.3 but 1:3.3-16ubuntu1 is to be installed Here is the output of apt-cache show clang-3.5: Package: clang-3.5 Priority: optional Section: universe/devel Installed-Size: 69658 Maintainer: Ubuntu Developers Original-Maintainer: LLVM Packaging Team Architecture: amd64 Source: llvm-toolchain-snapshot Version: 1:3.5-4ubuntu2~trusty2 Replaces: clang (= 2.15), libclang1-3.5 (= 1:3.5-4ubuntu2~trusty2), libedit2 (>= 2.11-20080614), libgcc1 (>= 1:4.1.1), libllvm3.5, libstdc++6 (>= 4.6), libtinfo5, libstdc++-4.8-dev, libgcc-4.8-dev, libobjc-4.8-dev, libclang-common-3.5-dev (= 1:3.5-4ubuntu2~trusty2), libc6-dev, binutils Recommends: llvm-3.5-dev, python Suggests: gnustep, gnustep-devel, clang-3.5-doc Breaks: clang-3.1, clang-3.2, clang-3.3, clang-3.4 ( Original-Maintainer: LLVM Packaging Team Architecture: amd64 Source: llvm-toolchain-snapshot Version: 1:3.5~svn201651-1ubuntu1 Replaces: clang, clang-3.1, clang-3.2, clang-3.3, clang-3.4, compiler-rt Provides: c++-compiler, c-compiler, objc-compiler Depends: libc6 (>= 2.15), libclang1-3.5 (= 1:3.5~svn201651-1ubuntu1), libgcc1 (>= 1:4.1.1), libllvm3.5, libstdc++6 (>= 4.6), libtinfo5, libstdc++-4.8-dev, libgcc-4.8-dev, libobjc-4.8-dev, libclang-common-3.5-dev (= 1:3.5~svn201651-1ubuntu1) Recommends: llvm-3.5-dev, python Breaks: clang, clang-3.1, clang-3.2, clang-3.3, clang-3.4, compiler-rt Filename: pool/universe/l/llvm-toolchain-snapshot/clang-3.5_3.5~svn201651-1ubuntu1_amd64.deb Size: 8828414 MD5sum: ffd2bc513809fc1f2905267fc99f4c02 SHA1: f73b30c4c5e22bad1b0daea5fc5309b52cc117b5 SHA256: 6b25a94eafb8e9cd8e7386835f1f0018dce2518b4fed529ca09c769fb5fcad84 Description-en: C, C++ and Objective-C compiler (LLVM based) Clang project is a C, C++, Objective C and Objective C++ front-end for the LLVM compiler. Its goal is to offer a replacement to the GNU Compiler Collection (GCC). . Clang implements all of the ISO C++ 1998 and 2001 standards and also provides a partial support of C++1y. Description-md5: 7a4488b4af767b7d9d9e5e4349a79fd5 Homepage: http://www.llvm.org/ Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Edit: here is the output of apt-cache policy: Package files: 100 /var/lib/dpkg/status release a=now 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ trusty/main Translation-en 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ trusty/main i386 Packages release v=14.04,o=LP-PPA-ubuntu-wine,a=trusty,n=trusty,l=Wine Team PPA,c=main origin ppa.launchpad.net 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ trusty/main amd64 Packages release v=14.04,o=LP-PPA-ubuntu-wine,a=trusty,n=trusty,l=Wine Team PPA,c=main origin ppa.launchpad.net 500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/ trusty/main Translation-en 500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/ trusty/main i386 Packages release v=14.04,o=LP-PPA-ubuntu-toolchain-r-test,a=trusty,n=trusty,l=Toolchain test builds,c=main origin ppa.launchpad.net 500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/ trusty/main amd64 Packages release v=14.04,o=LP-PPA-ubuntu-toolchain-r-test,a=trusty,n=trusty,l=Toolchain test builds,c=main origin ppa.launchpad.net 500 http://repo.steampowered.com/steam/ precise/steam i386 Packages release o=Valve Software LLC,n=precise,l=Steam,c=steam origin repo.steampowered.com 500 http://repo.steampowered.com/steam/ precise/steam amd64 Packages release o=Valve Software LLC,n=precise,l=Steam,c=steam origin repo.steampowered.com 500 http://archive.canonical.com/ubuntu/ trusty/partner Translation-en 500 http://archive.canonical.com/ubuntu/ trusty/partner i386 Packages release v=14.04,o=Canonical,a=trusty,n=trusty,l=Partner archive,c=partner origin archive.canonical.com 500 http://archive.canonical.com/ubuntu/ trusty/partner amd64 Packages release v=14.04,o=Canonical,a=trusty,n=trusty,l=Partner archive,c=partner origin archive.canonical.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe Translation-en 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted Translation-en 500 http://security.ubuntu.com/ubuntu/ trusty-security/multiverse Translation-en 500 http://security.ubuntu.com/ubuntu/ trusty-security/main Translation-en 500 http://security.ubuntu.com/ubuntu/ trusty-security/multiverse i386 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=multiverse origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe i386 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=universe origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted i386 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=restricted origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=main origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/multiverse amd64 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=multiverse origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=universe origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/restricted amd64 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=restricted origin security.ubuntu.com 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages release v=14.04,o=Ubuntu,a=trusty-security,n=trusty,l=Ubuntu,c=main origin security.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/multiverse Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/multiverse i386 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=multiverse origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe i386 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=universe origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted i386 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=restricted origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=main origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/multiverse amd64 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=multiverse origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=universe origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/restricted amd64 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=restricted origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages release v=14.04,o=Ubuntu,a=trusty-updates,n=trusty,l=Ubuntu,c=main origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/universe Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty/restricted Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty/multiverse Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty/main Translation-en 500 http://archive.ubuntu.com/ubuntu/ trusty/multiverse i386 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=multiverse origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=universe origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/restricted i386 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=restricted origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=main origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=multiverse origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=universe origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/restricted amd64 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=restricted origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages release v=14.04,o=Ubuntu,a=trusty,n=trusty,l=Ubuntu,c=main origin archive.ubuntu.com 700 http://extra.linuxmint.com/ rafaela/main i386 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=main origin extra.linuxmint.com 700 http://extra.linuxmint.com/ rafaela/main amd64 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=main origin extra.linuxmint.com 700 http://packages.linuxmint.com/ rafaela/import i386 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=import origin packages.linuxmint.com 700 http://packages.linuxmint.com/ rafaela/upstream i386 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=upstream origin packages.linuxmint.com 700 http://packages.linuxmint.com/ rafaela/main i386 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=main origin packages.linuxmint.com 700 http://packages.linuxmint.com/ rafaela/import amd64 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=import origin packages.linuxmint.com 700 http://packages.linuxmint.com/ rafaela/upstream amd64 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=upstream origin packages.linuxmint.com 700 http://packages.linuxmint.com/ rafaela/main amd64 Packages release v=17.2,o=linuxmint,a=rafaela,n=rafaela,l=linuxmint,c=main origin packages.linuxmint.com 500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ trusty/main Translation-en 500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ trusty/main i386 Packages release v=14.04,o=LP-PPA-kubuntu-ppa-backports,a=trusty,n=trusty,l=Kubuntu Backports,c=main origin ppa.launchpad.net 500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ trusty/main amd64 Packages release v=14.04,o=LP-PPA-kubuntu-ppa-backports,a=trusty,n=trusty,l=Kubuntu Backports,c=main origin ppa.launchpad.net 500 http://ppa.launchpad.net/kilian/f.lux/ubuntu/ trusty/main i386 Packages release v=14.04,o=LP-PPA-kilian-f.lux,a=trusty,n=trusty,l=f.lux indicator applet,c=main origin ppa.launchpad.net 500 http://ppa.launchpad.net/kilian/f.lux/ubuntu/ trusty/main amd64 Packages release v=14.04,o=LP-PPA-kilian-f.lux,a=trusty,n=trusty,l=f.lux indicator applet,c=main origin ppa.launchpad.net Pinned packages:
BlazePascal (1 rep)
Mar 4, 2016, 12:48 AM • Last activity: Dec 23, 2022, 02:03 AM
1 votes
1 answers
1835 views
Linux fedora how to change to older version of clang
I am currently using Linux fedora and I have the latest version of clang installed 14. I need an older version 12. Is there a way to do this through the terminal. I have been able to install the current version. Would I have to install the old library and change the path variables for it?
I am currently using Linux fedora and I have the latest version of clang installed 14. I need an older version 12. Is there a way to do this through the terminal. I have been able to install the current version. Would I have to install the old library and change the path variables for it?
Robert hause (21 rep)
Oct 11, 2022, 10:33 AM • Last activity: Oct 11, 2022, 07:41 PM
0 votes
1 answers
1973 views
Error to "install -y clang-9 libc++-9-dev libc++abi-9-dev"
I installed the Mistuba 2 package (https://github.com/mitsuba-renderer/mitsuba2) to be able to run btf-rendering (https://github.com/elerac/btf-rendering/). However, to install Mitsuba it is necessary to use clang9 and some other obsolete packages. When trying to install these packages, linux gives...
I installed the Mistuba 2 package (https://github.com/mitsuba-renderer/mitsuba2) to be able to run btf-rendering (https://github.com/elerac/btf-rendering/) . However, to install Mitsuba it is necessary to use clang9 and some other obsolete packages. When trying to install these packages, linux gives me an error message that I couldn't solve, but I suspect that it will be necessary to downgrade the system. Command to be executed: > sudo apt install -y clang-9 libc++-9-dev libc++abi-9-dev cmake ninja-build And the following error is generated: vitor-avancini@Nabucodonosor-desk:~$ sudo apt install -y clang-9 libc++-9-dev libc++abi-9-dev cmake ninja-build Reading package lists ... ready Building Dependency Tree ... Ready READING STATE INFORMATION ... READY Ninja-Build is already the latest version (1.10.1-1). Cmake is already the latest version (3.22.1-1ubuntu1.22.04.1). Some packages could not be installed. This may mean that You have requested an impossible situation or, if you are using the unstable distribution that some required packages were not Created still or were removed from the "Incoming". The following information can help solve the situation: The following packages have mismatched dependencies: lib32gcc-s1: Break: lib32gcc-s1 (<1:10) But 1: 8.4.0-1ubuntu1~18.04 is to be installed libc6-dev: Break: libc7-dev (<7.5.0-6 ~) but 7.5.0-3ubuntu1 ~ 18.04 is to be installed E: Impossible to correct problems, you kept broken packages. System Info: Kernel: 5.15.0-48-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.12 tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy How solve this problem?
V.Avancini (109 rep)
Sep 25, 2022, 06:06 PM • Last activity: Sep 27, 2022, 03:45 PM
1 votes
1 answers
420 views
Compiling a C program with Clang for MIPS (32-bit) on a FreeBSD x86_64/AMD64 system
Is there a way to compile a C program with Clang compiler for MIPS (32-bit) on a FreeBSD x86_64/AMD64 system?
Is there a way to compile a C program with Clang compiler for MIPS (32-bit) on a FreeBSD x86_64/AMD64 system?
ordinary_guy (29 rep)
Sep 25, 2022, 03:53 PM • Last activity: Sep 25, 2022, 09:33 PM
1 votes
1 answers
1145 views
Clang producing a symbol lookup error
i am getting this error whenever i run clang even with the --version flag ``` clang: symbol lookup error: /usr/lib/libclang-cpp.so.14: undefined symbol: _ZN4llvm9MDBuilder25createRTTIPointerPrologueEPNS_8ConstantES2_, version LLVM_14 ``` pacman -Qi llvm ``` Name : llvm Version : 14.0.6-3 Description...
i am getting this error whenever i run clang even with the --version flag
clang: symbol lookup error: /usr/lib/libclang-cpp.so.14: undefined symbol: _ZN4llvm9MDBuilder25createRTTIPointerPrologueEPNS_8ConstantES2_, version LLVM_14
pacman -Qi llvm
Name            : llvm
Version         : 14.0.6-3
Description     : Compiler infrastructure
Architecture    : x86_64
URL             : https://llvm.org/ 
Licenses        : custom:Apache 2.0 with LLVM Exception
Groups          : None
Provides        : None
Depends On      : llvm-libs  perl
Optional Deps   : None
Required By     : None
Optional For    : clang
Conflicts With  : None
Replaces        : None
Installed Size  : 368.51 MiB
Packager        : Evangelos Foutras 
Build Date      : Thu 04 Aug 2022 02:34:13 AM WAT
Install Date    : Mon 15 Aug 2022 09:49:26 AM WAT
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature
pacman -Qi clang
Name            : clang
Version         : 14.0.6-2
Description     : C language family frontend for LLVM
Architecture    : x86_64
URL             : https://clang.llvm.org/ 
Licenses        : custom:Apache 2.0 with LLVM Exception
Groups          : None
Provides        : clang-analyzer=14.0.6  clang-tools-extra=14.0.6
Depends On      : llvm-libs  gcc  compiler-rt
Optional Deps   : openmp: OpenMP support in clang with -fopenmp
                  python: for scan-view and git-clang-format [installed]
                  llvm: referenced by some clang headers [installed]
Required By     : lldb
Optional For    : qt5-tools
Conflicts With  : clang-analyzer  clang-tools-extra
Replaces        : clang-analyzer  clang-tools-extra
Installed Size  : 168.58 MiB
Packager        : Evangelos Foutras 
Build Date      : Thu 04 Aug 2022 02:44:58 AM WAT
Install Date    : Mon 15 Aug 2022 09:49:36 AM WAT
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature
causewe (11 rep)
Aug 15, 2022, 08:59 AM • Last activity: Aug 15, 2022, 02:37 PM
Showing page 1 of 20 total questions