Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
ERROR: dev-libs/dbus-glib-0.74 failed.
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German)
View previous topic :: View next topic  
Author Message
drehwanze
n00b
n00b


Joined: 27 Jan 2008
Posts: 13

PostPosted: Thu Mar 06, 2008 4:46 pm    Post subject: ERROR: dev-libs/dbus-glib-0.74 failed. Reply with quote

habe ein emerge --update --deep --newuse world gestartet, bei dev-libs/dbus-glib-0.74 war dann schluss.
wie kann ich notfalls das emergen fortsetzen und das alte packet mit 0.73 behalten, die Zeile =dev-libs/dbus-glib-0.73 ~amd64 in package.keywords hilft nicht.
Code:

* ERROR: dev-libs/dbus-glib-0.74 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2545:  Called econf 'src_compile' 'src_compile' '--disable-selinux' '--disable-verbose-mode' '--disable-checks' '--disable-asserts' '--with-xml=libxml' '--with-system-pid-file=/var/run/dbus.pid' '--with-system-socket=/var/run/dbus/system_bus_socket' '--with-session-socket-dir=/tmp' '--with-dbus-user=messagebus' '--localstatedir=/var'
 *               ebuild.sh, line  513:  Called die
 * The specific snippet of code:
libsandbox:  Can't resolve fopen: (null)
 *  The die message:
 *   econf failed
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-libs/dbus-glib-0.74/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/dbus-glib-0.74/temp/environment'.
 *

 * Messages for package dev-libs/dbus-glib-0.74:

 *
 * ERROR: dev-libs/dbus-glib-0.74 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2545:  Called econf 'src_compile' 'src_compile' '--disable-selinux' '--disable-verbose-mode' '--disable-checks' '--disable-asserts' '--with-xml=libxml' '--with-system-pid-file=/var/run/dbus.pid' '--with-system-socket=/var/run/dbus/system_bus_socket' '--with-session-socket-dir=/tmp' '--with-dbus-user=messagebus' '--localstatedir=/var'
 *               ebuild.sh, line  513:  Called die
 * The specific snippet of code:
 *  The die message:
 *   econf failed
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-libs/dbus-glib-0.74/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/dbus-glib-0.74/temp/environment'.


/var/tmp/portage/dev-libs/dbus-glib-0.74/temp/build.log
Code:

>>> Unpacking source...
>>> Unpacking dbus-glib-0.74.tar.gz to /var/tmp/portage/dev-libs/dbus-glib-0.74/work
  [32;01m* [0m Applying dbus-glib-introspection.patch ...
 [A [187C   [34;01m[  [32;01mok [34;01m ] [0m
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-libs/dbus-glib-0.74/work/dbus-glib-0.74 ...
 * econf: updating dbus-glib-0.74/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating dbus-glib-0.74/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-selinux --disable-verbose-mode --disable-checks --disable-asserts --with-xml=libxml --with-system-pid-file=/var/run/dbus.pid --with-system-socket=/var/run/dbus/system_bus_socket --with-session-socket-dir=/tmp --with-dbus-user=messagebus --localstatedir=/var --disable-doxygen-docs --disable-xml-docs --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu
libsandbox:  Can't resolve getcwd: (null)
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of x86_64-pc-linux-gnu-gcc... libsandbox:  Can't resolve getcwd: (null)
./configure: line 3737: ./depcomp: No such file or directory
none
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-pc-linux-gnu-g++... gcc3
checking for library containing strerror... none required
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking whether gcc understands -Wfloat-equal... yes
checking for a sed that does not truncate output... /bin/sed
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... libsandbox:  Can't resolve getcwd: (null)
x86_64-pc-linux-gnu-g++ -E
checking for x86_64-pc-linux-gnu-g77... no
checking for x86_64-pc-linux-gnu-xlf... no
checking for x86_64-pc-linux-gnu-f77... no
checking for x86_64-pc-linux-gnu-frt... no
checking for x86_64-pc-linux-gnu-pgf77... no
checking for x86_64-pc-linux-gnu-cf77... no
checking for x86_64-pc-linux-gnu-fort77... no
checking for x86_64-pc-linux-gnu-fl32... no
checking for x86_64-pc-linux-gnu-af77... no
checking for x86_64-pc-linux-gnu-xlf90... no
checking for x86_64-pc-linux-gnu-f90... no
checking for x86_64-pc-linux-gnu-pgf90... no
checking for x86_64-pc-linux-gnu-pghpf... no
checking for x86_64-pc-linux-gnu-epcf90... no
checking for x86_64-pc-linux-gnu-gfortran... x86_64-pc-linux-gnu-gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether x86_64-pc-linux-gnu-gfortran accepts -g... yes
checking the maximum length of command line arguments... 4096
checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... failed
checking for objdir... .libs
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by x86_64-pc-linux-gnu-g++... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking for x86_64-pc-linux-gnu-g++ option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-g++ PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-g++ static flag -static works... yes
checking if x86_64-pc-linux-gnu-g++ supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for x86_64-pc-linux-gnu-gfortran option to produce PIC... -fPIC
checking if x86_64-pc-linux-gnu-gfortran PIC flag -fPIC works... yes
checking if x86_64-pc-linux-gnu-gfortran static flag -static works... yes
checking if x86_64-pc-linux-gnu-gfortran supports -c -o file.o... yes
checking whether the x86_64-pc-linux-gnu-gfortran linker (/usr/x86_64-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for char... yes
checking size of char... 1
checking for short... yes
checking size of short... 2
checking for long... yes
checking size of long... 8
checking for int... yes
checking size of int... configure: error: cannot compute sizeof (int)
See `config.log' for more details.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-libs/dbus-glib-0.74/work/dbus-glib-0.74/config.log
  [31;01m* [0m
  [31;01m* [0m ERROR: dev-libs/dbus-glib-0.74 failed.
  [31;01m* [0m Call stack:
  [31;01m* [0m               ebuild.sh, line   49:  Called src_compile
  [31;01m* [0m             environment, line 2545:  Called econf 'src_compile' 'src_compile' '--disable-selinux' '--disable-verbose-mode' '--disable-checks' '--disable-asserts' '--with-xml=libxml' '--with-system-pid-file=/var/run/dbus.pid' '--with-system-socket=/var/run/dbus/system_bus_socket' '--with-session-socket-dir=/tmp' '--with-dbus-user=messagebus' '--localstatedir=/var'
  [31;01m* [0m               ebuild.sh, line  513:  Called die
  [31;01m* [0m The specific snippet of code:
libsandbox:  Can't resolve fopen: (null)
  [31;01m* [0m  The die message:
  [31;01m* [0m   econf failed
  [31;01m* [0m
  [31;01m* [0m If you need support, post the topmost build error, and the call stack if relevant.
  [31;01m* [0m A complete build log is located at '/var/tmp/portage/dev-libs/dbus-glib-0.74/temp/build.log'.
  [31;01m* [0m The ebuild environment file is located at '/var/tmp/portage/dev-libs/dbus-glib-0.74/temp/environment'.
  [31;01m* [0m
Back to top
View user's profile Send private message
Max Steel
Advocate
Advocate


Joined: 12 Feb 2007
Posts: 2273
Location: My own world! I and Gentoo!

PostPosted: Thu Mar 06, 2008 4:49 pm    Post subject: Reply with quote

Code:
libsandbox:  Can't resolve fopen: (null)


Das sieht so aus, als ob das helfen könnt,
emerge -a1 sandbox

Wenn das nicht hilft ein FEATURES="-sandbox" emerge -a1 sandbox
_________________
mfg
Steel
___________________

Heim-PC: AMD Ryzen 5950X, 64GB RAM, GTX 1080
Laptop: Intel Core i5-4300U, 16GB RAM, Intel Graphic
Arbeit-PC: Intel i5-1145G7, 16GB RAM, Intel Iris Xe Graphic (leider WSL2)
Back to top
View user's profile Send private message
drehwanze
n00b
n00b


Joined: 27 Jan 2008
Posts: 13

PostPosted: Thu Mar 06, 2008 5:17 pm    Post subject: Reply with quote

Das FEATURES="-sandbox" emerge -a1 sandbox hat geholfen. Danke dafür.
Aber was genau ist jetzt passiert, kann ich irgendwo mehr infos erhalten.
Sollte ich sandbox in die make.conf aufnehmen um solche Probleme in Zukunft zu vermeiden?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum