I'm having a hard time trying to compile cups-filters-1.14.0 on Centos 6. Now, after hours of installing dependencies I get this:
gdbus-codegen \
--interface-prefix org.cups.cupsd \
--c-namespace Cups \
--generate-c-code cups-notifier \
utils/org.cups.cupsd.Notifier.xml
make: gdbus-codegen: Command not found
make: *** [cups-notifier.c] Error 127
How can I install gdbus-codegen ?
Related
I am trying to compile Swift code via AWS Lambda.
Therefore I am using an Ubuntu 18.04 Image as base.
The Swift Version is 5.0.1.
When the image is executed locally, it works fine.
When I try to execute it in AWS Lambda, I get the following error:
/usr/bin/ld.gold: fatal error: /tmp/project/src/a.out: Operation not
permitted\nclang-7: error: linker command failed with exit code 1 (use
-v to see invocation)
I think that the problem is caused by the read-only aws lambda container, that only allows to write into the /tmp/ folder.
Do you know how to fix this error? It seems that swift needs permissions for folders, it doesnt have permission for?
Dockerfile
FROM ubuntu:18.04
# install clang
RUN apt-get update
RUN apt-get install -y clang
# install wget
RUN apt-get install -y wget
# install swift dependencies
RUN apt-get install -y libcurl3 libpython2.7 libpython2.7-dev
ARG DEBIAN_FRONTEND=noninteractive
RUN apt-get install -y --no-install-recommends \
binutils \
git \
libc6-dev \
libcurl4 \
libedit2 \
libgcc-5-dev \
libpython2.7 \
libsqlite3-0 \
libstdc++-5-dev \
libxml2 \
pkg-config \
tzdata \
zlib1g-dev \
libbsd-dev
RUN apt-get install -y libicu-dev
# install swift 5.0.1
RUN wget https://swift.org/builds/swift-5.0.1-release/ubuntu1804/swift-5.0.1-RELEASE/swift-5.0.1-RELEASE-ubuntu18.04.tar.gz RUN tar xzf swift-5.0.1-RELEASE-ubuntu18.04.tar.gz RUN mv swift-5.0.1-RELEASE-ubuntu18.04 /usr/lib/swift RUN echo "export PATH=/usr/lib/swift/usr/bin:$PATH" >> ~/.bashrc
RUN . ~/.bashrc
RUN chmod -R o+r /usr/lib/swift
This is the command executed in the AWS-Lambda handler function:
swiftc hello_world.swift -o a.out
hello_world.swift
print("Hello World!")
Your output must be set in tmp folder
swiftc hello_world.swift -o /tmp/a.out
I have been trying to install xv6 using the following commands:
sudo apt-get install qemu
sudo apt-get install libc6-dev-i386
tar xzvf xv6-rev11.tar.gz
cd xv6-public
make
make qemu
I get the following error while running make qemu command
qemu-system-i386 -serial mon:stdio -drive file=fs.img,index=1,media=disk,format=raw -drive file=xv6.img,index=0,media=disk,format=raw -smp 2 -m 512
make: qemu-system-i386: Command not found
make: *** [Makefile:225: qemu] Error 127
As suggested at various places, I have un-commented line 54 QEMU = qemu-system-i386 in the makefile before executing make qemu
Please help me fix the error. Thanks in advance ...
You need to install the package containing qemu-system-i386.
After a little search on https://packages.ubuntu.com, you can find the right package: qemu-system-x86.
To install the missing package, type
sudo apt install qemu-system-x86
I am trying to install a Perl Module Bio::Tools::Run::Alignment::Muscle. I am using this docker image:
FROM ubuntu:16.04
RUN echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections
RUN apt-get update && apt-get install -y software-properties-common
RUN apt-add-repository multiverse
RUN add-apt-repository restricted
RUN apt-get update && apt-get install -y \
wget \
unzip \
sudo \
make \
gcc \
libdb-dev \
libgd-dev \
zlib1g-dev \
libxml2-dev \
libexpat1-dev \
pkg-config \
graphviz \
libssl-dev \
cpanminus
# Dependencies
RUN cpanm File::Sort Config::Any Bio::FeatureIO Bio::Cluster::SequenceFamily
# Install problematic ::Muscle
RUN cpanm Net::SSLeay LWP::Protocol::https Bio::Tools::Eponine
RUN cpanm Bio::DB::EUtilities # Ensembl requirement
When I try to install with cpanm by entering the container and typing "cpanm Bio::Tools::Run::Alignment::Muscle", I get the following error:
Test Summary Report
-------------------
t/Eponine.t (Wstat: 65280 Tests: 2 Failed: 0)
Non-zero exit status: 255
Parse errors: Bad plan. You planned 7 tests but ran 2.
Files=70, Tests=2068, 15 wallclock secs ( 0.32 usr 0.09 sys + 12.22 cusr 1.33 csys = 13.96 CPU)
Result: FAIL
Failed 1/70 test programs. 0/2068 subtests failed.
-> FAIL Installing Bio::Tools::Run::Alignment::Muscle failed. See /root/.cpanm/work/1552304305.41131/build.log for details. Retry with --force to force install it.
Is there a way to debug this, and check if this is safe to ignore?
You need to install Java for a successful t/Eponine.t test.
There is an error in line:
open(my $PIPE,"java -version 2>&1 |") || exit;
If Java not installed the test just exits and the test plan fails.
I'm using a RaspberryPi Zero W with Raspbian 4.9.80+ and I'm trying to install LTTng-modules-2.8 but when I type these commands
wget http://lttng.org/files/lttng-modules/lttng-modules-latest-
2.8.tar.bz2 &&
tar -xf lttng-modules-latest-2.8.tar.bz2 &&
cd lttng-modules-2.8.* &&
make &&
sudo make modules_install &&
sudo depmod -a
I receive this (after typing the command "make"):
make -C /lib/modules/4.9.80+/build M=/home/pi/lttng-modules-2.8.7
CONFIG_LTTNG=m
CONFIG_LTTNG_CLOCK_PLUGIN_TEST=m modules
make[1]: *** /lib/modules/4.9.80+/build: No such file or directory. Stop.
Makefile:110: receipe for target 'modules' failed
make: *** [modules] Error 2
I downloaded the modules correctly but it seems that they are not there; how can I solve this problem?
Thanks, Ivan.
You need the kernel headers to build modules, according to raspbian's documentation they are provided by the raspberrypi-kernel-headers, you can install it with this command :
sudo apt-get install raspberrypi-kernel-headers
And then run the make commands.
I find problems when I started to compile openjdk for my first time.
Below is what I did
hg clone http://hg.openjdk.java.net/jdk9/dev 9dev
cd 9dev
bash ./get_source.sh
bash ./configure
Then, I got this error message
configure: error: Could not find X11 libraries. You might be able to fix this by running 'sudo yum install libXtst-devel libXt-devel libXrender-devel libXi-devel'.
Then, I did what it told me to do.
After the installation, the same error still exists.
So I checked where the files lies on my machine
rpm -qa | grep X11
libX11-1.6.3-3.el7.x86_64
libX11-common-1.6.3-3.el7.noarch
libX11-devel-1.6.3-3.el7.x86_64
rpm -ql libX11-1.6.3-3.el7.x86_64
/usr/lib64/libX11-xcb.so.1
/usr/lib64/libX11-xcb.so.1.0.0
/usr/lib64/libX11.so.6
/usr/lib64/libX11.so.6.3.0
so i tried the way of specifying the X11 path
bash ./configure --x-libraries=/usr/lib64
Unfortunately, the same error still stays.
Can someone help me out of here, please?
thx
update
Thank #omajid for directing me to the log file config.log, where I found that the configure is using the gcc in my linuxbrew installation.
configure:56234: /data/alex/git/brew/bin/g++ -o conftest conftest.cpp -lX11 >&5
/data/alex/git/brew/bin/ld: cannot find -lX11
collect2: error: ld returned 1 exit status
configure:56234: $? = 1
So after I exported my c compiler to the system one, the problem was fixed.
export CC=/usr/bin/gcc
export CXX=/usr/bin/g++
Here is the relevant packages needed at build time and the configure flags I use in my spec file for building unofficial OpenJDK 9 packages for Fedora/EPEL:
autoconf
automake
alsa-lib-devel
binutils
cups-devel
desktop-file-utils
fontconfig
freetype-devel
elfutils
giflib-devel
gcc-c++
gdb
gtk2-devel
lcms2-devel
libjpeg-devel
libpng-devel
libxslt
libX11-devel
libXi-devel
libXinerama-devel
libXt-devel
libXtst-devel
nss-devel
pkgconfig
xorg-x11-proto-devel
zip
java-1.8.0-openjdk-devel
bash ../configure \
--with-boot-jdk=/usr/lib/jvm/java-1.8.0-openjdk/ \
--with-native-debug-symbols=internal \
--enable-unlimited-crypto \
--with-zlib=system \
--with-libjpeg=system \
--with-giflib=system \
--with-libpng=system \
--with-lcms=system \
--with-stdc++lib=dynamic \
--disable-javac-server \
--disable-warnings-as-errors
In any case, the error messages produce by configure are a best guess. You should take a look at config.log to see what test actually failed and what the error messages are. In this case, it looks like you are probably missing one of several X11 libraries. Possibly libXinerama-devel.
If this still doesn't fix your error, please paste the error messages from your autoconf log file (should be named config.log or configure.log, I forget).