LinuxQuestions.org - Unable to emerge xorg, circular dependencies

- Gentoo (https://www.linuxquestions.org/questions/gentoo-87/)

- - Unable to emerge xorg, circular dependencies (https://www.linuxquestions.org/questions/gentoo-87/unable-to-emerge-xorg-circular-dependencies-4175445923/)

Unable to emerge xorg, circular dependencies

I have followed the guide at http://www.gentoo.org/doc/en/xorg-config.xml and arrived at the following problem when I try to emerge xorg-server:

Code:



 * IMPORTANT: config file '/etc/portage/package.use' needs updating.

 * See the CONFIGURATION FILES section of the emerge

 * man page to learn how to update config files.

Calculating dependencies... done!





[nomerge      ] x11-base/xorg-server-1.13.1  USE="ipv6 nptl (selinux) suid udev xorg -dmx -doc -kdrive -minimal -static-libs -tslib -xnest -xvfb" 

[nomerge      ]  x11-base/xorg-drivers-1.13  INPUT_DEVICES="evdev -acecad -aiptek -elographics -fpit -hyperpen -joystick -keyboard -mouse -mutouch -penmount -synaptics -tslib -vmmouse -void -wacom" VIDEO_CARDS="radeon -apm -ark -ast -chips -cirrus -dummy -epson -fbdev -fglrx -geode -glint -i128 -i740 -intel -mach64 -mga -modesetting -neomagic (-newport) -nouveau -nv (-nvidia) (-omap) (-omapfb) -qxl -r128 -rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx -tga -trident -tseng -v4l -vesa -via -virtualbox -vmware (-voodoo)" 

[ebuild  N    ]  x11-drivers/xf86-input-evdev-2.7.3  357 kB

[ebuild  N    ]  x11-drivers/xf86-video-ati-7.0.0  USE="udev (-glamor)" 758 kB

[ebuild  N    ]  media-libs/mesa-9.0.1  USE="classic egl gallium llvm nptl pax_kernel pic (selinux) shared-glapi xorg -bindist -debug -g3dvl -gbm -gles1 -gles2 -openvg -osmesa -r600-llvm-compiler -vdpau (-wayland) -xa -xvmc" VIDEO_CARDS="radeon -i915 -i965 -intel -nouveau -r100 -r200 -r300 -r600 -radeonsi -vmware" 5,973 kB

[ebuild  N    ]  x11-base/xorg-server-1.13.1  USE="ipv6 nptl (selinux) suid udev xorg -dmx -doc -kdrive -minimal -static-libs -tslib -xnest -xvfb" 5,352 kB



Total: 4 packages (4 new), Size of downloads: 12,438 kB



 * Error: circular dependencies:



(media-libs/mesa-9.0.1::gentoo, ebuild scheduled for merge) depends on

 (x11-base/xorg-server-1.13.1::gentoo, ebuild scheduled for merge) (buildtime)

  (media-libs/mesa-9.0.1::gentoo, ebuild scheduled for merge) (buildtime)



It might be possible to break this cycle

by applying the following change:

- media-libs/mesa-9.0.1 (Change USE: -xorg)



Note that this change can be reverted, once the package has been installed.



!!! Multiple package instances within a single package slot have been pulled

!!! into the dependency graph, resulting in a slot conflict:



dev-lang/swig:0



  (dev-lang/swig-2.0.8::gentoo, installed) pulled in by

    >=dev-lang/swig-2.0.4-r1 required by (sys-libs/libsemanage-2.1.9::gentoo, ebuild scheduled for merge)

    (and 1 more with the same problem)



  (dev-lang/swig-1.3.40-r1::gentoo, ebuild scheduled for merge) pulled in by

    <dev-lang/swig-2.0 required by (app-admin/setools-3.3.7-r6::gentoo, ebuild scheduled for merge)



dev-libs/libxml2:2



  (dev-libs/libxml2-2.8.0-r3::gentoo, installed) pulled in by

    (no parents that aren't satisfied by other packages in this slot)



  (dev-libs/libxml2-2.8.0-r3::gentoo, ebuild scheduled for merge) pulled in by

    dev-libs/libxml2[python] required by (media-libs/mesa-9.0.1::gentoo, ebuild scheduled for merge)





It may be possible to solve this problem by using package.mask to

prevent one of those packages from being selected. However, it is also

possible that conflicting dependencies exist such that they are

impossible to satisfy simultaneously.  If such a conflict exists in

the dependencies of two different packages, then those packages can

not be installed simultaneously.



For more information, see MASKED PACKAGES section in the emerge man

page or refer to the Gentoo Handbook.

My /etc/portage/make.conf reads:

Code:

# These settings were set by the catalyst build script that automatically

# built this stage.

# Please consult /usr/share/portage/config/make.conf.example for a more

# detailed example.

CFLAGS="-O2 -march=athlon-xp -pipe"

CXXFLAGS="${CFLAGS}"

# WARNING: Changing your CHOST is not something that should be done lightly.

# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.

CHOST="i686-pc-linux-gnu"

# These are the USE flags that were used in addition to what is provided by the

# profile used for building.

USE="bindist"



GENTOO_MIRRORS="http://ftp.df.lth.se/pub/gentoo/ rsync://ftp.df.lth.se/pub/gentoo/ ftp://ftp.df.lth.se/pub/gentoo/"



SYNC="rsync://rsync5.se.gentoo.org/gentoo-portage"



USE="xorg udev libkms gtk gnome alsa python -kde"



INPUT_DEVICES="evdev"

VIDEO_CARDS="radeon"

Why does my make.conf need updating? What is wrong? Before when I ran emerge xorg-server I got a few missing USE variables, which I have added in.

I'm not sure why this happened, but I recommend you emerge mesa with -xorg, then emerge xorg, then re-emerge mesa with +xorg. Stupid I know but maybe it will work for you.

Also, I noticed the message about your package.use file needing updating. Could you post it please?

Quote:

Originally Posted by vik (Post 4871726)

Thanks, I've been compiling mesa for a while now and will complete the additional steps once that process if finished (this is a slow system).

My /etc/portage/package.use file contains:

Code:

x11-base/xorg-server udev

Quote:

Originally Posted by vik (Post 4871726)

I was able to emerge mesa, but not able to emerge xorg-server after that (I emerged mesa with -xorg but removed the '-' when attempting to emerge xorg-server).

Errors I got when emerging xorg-server after having first emerged mesa are as follows:

Code:

make[1]: Entering directory `/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7/libapol/swig/python-2.7'

i686-pc-linux-gnu-gcc -std=gnu99 -shared -o _apol.so.4.3 apol_wrap.c -fno-strict-aliasing  -I/usr/include -I/usr/include -I../../../libqpol/include -I../../.. -fpic -I../../../libapol/include -O2 -march=athlon-xp -pipe -I/usr/include/python2.7 ../../../libapol/src/libapol.so ../../../libqpol/src/libqpol.so -Wl,-O1 -Wl,--as-needed -Wl,-soname,_apol.so.4

apol_wrap.c:3513:19: error: conflicting types for 'apol_vector_get_size'

../../../libapol/include/apol/vector.h:166:16: note: previous declaration of 'apol_vector_get_size' was here

apol_wrap.c:3523:19: error: conflicting types for 'apol_vector_get_capacity'

../../../libapol/include/apol/vector.h:178:16: note: previous declaration of 'apol_vector_get_capacity' was here

apol_wrap.c:3536:18: error: conflicting types for 'apol_vector_get_element'

../../../libapol/include/apol/vector.h:189:15: note: previous declaration of 'apol_vector_get_element' was here

apol_wrap.c:3539:17: error: conflicting types for 'apol_vector_append'

../../../libapol/include/apol/vector.h:224:13: note: previous declaration of 'apol_vector_append' was here

apol_wrap.c: In function 'apol_vector_append':

apol_wrap.c:3541:3: error: void value not ignored as it ought to be

apol_wrap.c: At top level:

apol_wrap.c:3548:17: error: conflicting types for 'apol_vector_append_unique'

../../../libapol/include/apol/vector.h:246:13: note: previous declaration of 'apol_vector_append_unique' was here

apol_wrap.c: In function 'apol_vector_append_unique':

apol_wrap.c:3550:3: error: too many arguments to function 'apol_vector_append_unique'

apol_wrap.c:3548:17: note: declared here

apol_wrap.c:3550:3: error: void value not ignored as it ought to be

apol_wrap.c: At top level:

apol_wrap.c:3557:17: error: conflicting types for 'apol_vector_cat'

../../../libapol/include/apol/vector.h:257:13: note: previous declaration of 'apol_vector_cat' was here

apol_wrap.c: In function 'apol_vector_cat':

apol_wrap.c:3559:3: error: void value not ignored as it ought to be

apol_wrap.c: At top level:

apol_wrap.c:3566:17: error: conflicting types for 'apol_vector_remove'

../../../libapol/include/apol/vector.h:269:13: note: previous declaration of 'apol_vector_remove' was here

apol_wrap.c: In function 'apol_vector_remove':

apol_wrap.c:3568:3: error: void value not ignored as it ought to be

apol_wrap.c: At top level:

apol_wrap.c:3575:17: error: conflicting types for 'apol_vector_sort'

../../../libapol/include/apol/vector.h:311:14: note: previous declaration of 'apol_vector_sort' was here

apol_wrap.c: In function 'apol_vector_sort':

apol_wrap.c:3576:3: error: too many arguments to function 'apol_vector_sort'

apol_wrap.c:3575:17: note: declared here

apol_wrap.c: At top level:

apol_wrap.c:3578:17: error: conflicting types for 'apol_vector_sort_uniquify'

../../../libapol/include/apol/vector.h:329:14: note: previous declaration of 'apol_vector_sort_uniquify' was here

apol_wrap.c: In function 'apol_vector_sort_uniquify':

apol_wrap.c:3579:3: error: too many arguments to function 'apol_vector_sort_uniquify'

...

A LOT of errors follow this.

Then eventually I get:

Code:

make[1]: *** [_apol.so.4.3] Error 1

make[1]: Leaving directory `/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7/libapol/swig/python-2.7'

make: *** [all] Error 2

emake failed

 * ERROR: app-admin/setools-3.3.7-r3 failed (compile phase):

 *  Building of Python bindings from libapol/swig/python directory with CPython 2.7 failed

 * 

 * Call stack:

 *    ebuild.sh, line  93:  Called src_compile

 *  environment, line 7135:  Called python_execute_function '--action-message' 'Building of Python bindings from libapol/swig/python directory with $(python_get_implementation) $(python_get_version)' '--failure-message' 'Building of Python bindings from libapol/swig/python directory with $(python_get_implementation) $(python_get_version) failed' '-s' '--source-dir' 'libapol/swig/python' 'building'

 *  environment, line 5453:  Called die

 * The specific snippet of code:

 *                      die "${failure_message}";

 * 

 * If you need support, post the output of `emerge --info '=app-admin/setools-3.3.7-r3'`,

 * the complete build log and the output of `emerge -pqv '=app-admin/setools-3.3.7-r3'`.

!!! When you file a bug report, please include the following information:

GENTOO_VM=  CLASSPATH="" JAVA_HOME=""

JAVACFLAGS="" COMPILER=""

and of course, the output of emerge --info

 * The complete build log is located at '/var/tmp/portage/app-admin/setools-3.3.7-r3/temp/build.log'.

 * The ebuild environment file is located at '/var/tmp/portage/app-admin/setools-3.3.7-r3/temp/environment'.

 * Working directory: '/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7/libapol/swig/python-2.7'

 * S: '/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7'



>>> Failed to emerge app-admin/setools-3.3.7-r3, Log file:



>>>  '/var/tmp/portage/app-admin/setools-3.3.7-r3/temp/build.log'



 * Messages for package media-libs/freetype-2.4.9-r1:



 * The TrueType bytecode interpreter is no longer patented and thus no

 * longer controlled by the bindist USE flag.  Enable the auto-hinter

 * USE flag if you want the old USE=bindist hinting behavior.



 * Messages for package app-admin/setools-3.3.7-r3:



 * ERROR: app-admin/setools-3.3.7-r3 failed (compile phase):

 *  Building of Python bindings from libapol/swig/python directory with CPython 2.7 failed

 * 

 * Call stack:

 *    ebuild.sh, line  93:  Called src_compile

 *  environment, line 7135:  Called python_execute_function '--action-message' 'Building of Python bindings from libapol/swig/python directory with $(python_get_implementation) $(python_get_version)' '--failure-message' 'Building of Python bindings from libapol/swig/python directory with $(python_get_implementation) $(python_get_version) failed' '-s' '--source-dir' 'libapol/swig/python' 'building'

 *  environment, line 5453:  Called die

 * The specific snippet of code:

 *                      die "${failure_message}";

 * 

 * If you need support, post the output of `emerge --info '=app-admin/setools-3.3.7-r3'`,

 * the complete build log and the output of `emerge -pqv '=app-admin/setools-3.3.7-r3'`.

 * The complete build log is located at '/var/tmp/portage/app-admin/setools-3.3.7-r3/temp/build.log'.

 * The ebuild environment file is located at '/var/tmp/portage/app-admin/setools-3.3.7-r3/temp/environment'.

 * Working directory: '/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7/libapol/swig/python-2.7'

 * S: '/var/tmp/portage/app-admin/setools-3.3.7-r3/work/setools-3.3.7'



 * GNU info directory index is up-to-date.



 * IMPORTANT: config file '/etc/portage/package.use' needs updating.

 * See the CONFIGURATION FILES section of the emerge

 * man page to learn how to update config files.

OK, this is making a bit more sense. The emerge errors all seem related to some selinux packages: setools and libsemanage not xorg. It looks like your first problem is related to setools needing swig version 1.3.40-r1 and libsemanage needing swig-2.0.8 (which you've already installed). I guess swig doesn't do slotting so this is a problem. Just to see if any problems in the source tree have been resolved, have you run emerge --sync recently and emerge -puND world?

1) maybe try the ~x86 or ~amd64 version of setools and see if it will accept your swig 2.0.8.
2) another option would be to see what packages depend on libsemanage and setools and see if you can get rid of one of them (thus removing the conflicting dependency on swig).