You are not logged in.
i am using gcc-multilib, gcc-fortran to prevent my system from upgrade.
so i have to remove gcc-fortran, then everything works fine.
# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
warning: linux: ignoring package upgrade (3.12.7-2 => 3.14.2-1)
resolving dependencies...
looking for inter-conflicts...
:: gcc-libs and gcc-libs-multilib are in conflict. Remove gcc-libs-multilib? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: gcc-libs and gcc-libs-multilib are in conflict
# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
warning: linux: ignoring package upgrade (3.12.7-2 => 3.14.2-1)
resolving dependencies...
looking for inter-conflicts...
:: gcc-libs and gcc-libs-multilib are in conflict. Remove gcc-libs-multilib? [y/N] y
:: gcc and gcc-multilib are in conflict. Remove gcc-multilib? [y/N] y
Packages (17): cinnamon-screensaver-2.2.3-1 gcc-4.9.0-2 gcc-fortran-4.9.0-2 gcc-libs-4.9.0-2
gcc-libs-multilib-4.9.0-1 [removal] gcc-multilib-4.9.0-1 [removal] gtkspell3-3.0.6-1 gvfs-1.20.2-1
intel-dri-10.1.3-1 libtracker-sparql-1.0.1-1 man-pages-3.66-1 mesa-10.1.3-1 mesa-libgl-10.1.3-1
nemo-2.2.1-2 nspr-4.10.5-1 nss-3.16.1-1 pacman-4.1.2-6
...
[INSTALLED]
...
# pacman -S gcc-multilib
resolving dependencies...
looking for inter-conflicts...
:: gcc-libs-multilib and gcc-libs are in conflict. Remove gcc-libs? [y/N] y
:: gcc-multilib and gcc are in conflict. Remove gcc? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc-fortran: requires gcc=4.9.0-2
# pacman -R gcc-fortran
checking dependencies...
Packages (1): gcc-fortran-4.9.0-2
Total Removed Size: 16.79 MiB
# pacman -S gcc-multilib
resolving dependencies...
looking for inter-conflicts...
:: gcc-libs-multilib and gcc-libs are in conflict. Remove gcc-libs? [y/N] y
:: gcc-multilib and gcc are in conflict. Remove gcc? [y/N] y
Packages (4): gcc-4.9.0-2 [removal] gcc-libs-4.9.0-2 [removal] gcc-libs-multilib-4.9.0-1 gcc-multilib-4.9.0-1Last edited by mmix (2014-05-10 01:31:13)
Offline
It's simply because the multilib version hasn't been updated to pkgver 2 yet. You could always use gcc-fortran-multilib.
Last edited by Scimmia (2014-05-10 01:44:14)
Offline
Using multilib is all or none...
pacman -S gcc-multilib gcc-fortran-multilibOffline
at first, i was using gcc, then i need gcc-multilib for some reason,
so i have installed it, using it for now,
what i don't understand is why gcc-fortran was not removed at the time.
and i don't need fortran at all. time is lack for better programming language such like lisp, c compiler, clojure, scala, nimrod, etc.etc.
Last edited by mmix (2014-05-10 02:03:24)
Offline
Using multilib is all or none...
pacman -S gcc-multilib gcc-fortran-multilib
Allan, i agree it should be like that but the reality is different.
afaict gcc-multilib provide all functionality that gcc-libs does PLUS the 32-bit compiled to work in x86_64 environment stuff.
So all gcc-multilib pacakges provide their non-multilb counterpart.
From a technical point this is correct, but the downside is that it's possible to mix multilib with non-multilib versions on the same install .
That mix possibility is what causes problems.
I can think of some ways to solve this :
differ gcc packages between i686 and i686 :
build gcc for i686 as it is now
for x86_64 only provide gcc with multilib functionality
(basically this would mean renaming gc--multilib to gcc and moving it from multilib repo to core, along with necessary makedepends).
This would mean gcc multilib functionality is forced on all x86_64 users, doubt if that is a good idea.
alternative :
Add a conflicts clause for gcc-libs-multilib to all gcc non-multilib programs.
example : gcc-fortran would have conflicts=(gcc-libs-mutilib)
That means users have to choose between multilib and non-multilib, but doesn't force multilib on all x86_64 users.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online