HI, everyone,
I am still having the update issue with gcc. I will follow this message
with the error received from "yum update".

Also my processor is periodically locking up. Is anyone else
experiencing either of these errors? When it locks up, it is running
one of the cores at or near 100%, and the dbus daemon is running at 54%,
and if I click the x box on system monitor, the window remains open, but
the process appears to have died.

I am trying to figure out if these are related or separate issues that
I have to resolve.

Can anyone offer any guidance, and as to the update of gcc, there was
an earlier email where someone indicated that a update was needed but
not available yet. Any help on that front either?

Regards,
Les H

# yum install gcc-c++.x86_64
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc-c++ = 4.6.2 for package:
clang-2.9-6.fc16.x86_64
---> Package gcc-c++.x86_64 0:4.6.3-2.fc16 will be an update
--> Processing Dependency: libstdc++-devel = 4.6.3-2.fc16 for package:
gcc-c++-4.6.3-2.fc16.x86_64
--> Processing Dependency: libstdc++ = 4.6.3-2.fc16 for package: gcc-c
++-4.6.3-2.fc16.x86_64
--> Processing Dependency: gcc = 4.6.3-2.fc16 for package: gcc-c
++-4.6.3-2.fc16.x86_64
--> Running transaction check
---> Package gcc.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc = 4.6.2-1.fc16 for package:
gcc-java-4.6.2-1.fc16.x86_64
--> Processing Dependency: gcc = 4.6.2 for package:
libtool-2.4-8.fc16.x86_64
---> Package gcc.x86_64 0:4.6.3-2.fc16 will be an update
--> Processing Dependency: libgomp = 4.6.3-2.fc16 for package:
gcc-4.6.3-2.fc16.x86_64
--> Processing Dependency: cpp = 4.6.3-2.fc16 for package:
gcc-4.6.3-2.fc16.x86_64
--> Processing Dependency: libgcc >= 4.6.3-2.fc16 for package:
gcc-4.6.3-2.fc16.x86_64
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc-c++ = 4.6.2 for package:
clang-2.9-6.fc16.x86_64
---> Package libstdc++.i686 0:4.6.2-1.fc16 will be updated
---> Package libstdc++.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libstdc++.i686 0:4.6.3-2.fc16 will be an update
---> Package libstdc++.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libstdc++-devel.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libstdc++-devel.x86_64 0:4.6.3-2.fc16 will be an update
--> Running transaction check
---> Package cpp.x86_64 0:4.6.2-1.fc16 will be updated
---> Package cpp.x86_64 0:4.6.3-2.fc16 will be an update
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc-c++ = 4.6.2 for package:
clang-2.9-6.fc16.x86_64
---> Package gcc-java.x86_64 0:4.6.2-1.fc16 will be updated
---> Package gcc-java.x86_64 0:4.6.3-2.fc16 will be an update
--> Processing Dependency: libgcj-devel = 4.6.3-2.fc16 for package:
gcc-java-4.6.3-2.fc16.x86_64
--> Processing Dependency: libgcj = 4.6.3-2.fc16 for package:
gcc-java-4.6.3-2.fc16.x86_64
---> Package libgcc.i686 0:4.6.2-1.fc16 will be updated
---> Package libgcc.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgcc.i686 0:4.6.3-2.fc16 will be an update
---> Package libgcc.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgomp.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgomp.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libtool.x86_64 0:2.4-8.fc16 will be updated
---> Package libtool.x86_64 0:2.4-9.fc16 will be an update
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc-c++ = 4.6.2 for package:
clang-2.9-6.fc16.x86_64
---> Package libgcj.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgcj.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgcj-devel.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgcj-devel.x86_64 0:4.6.3-2.fc16 will be an update
--> Finished Dependency Resolution
Error: Package: clang-2.9-6.fc16.x86_64 (@updates)
Requires: gcc-c++ = 4.6.2
Removing: gcc-c++-4.6.2-1.fc16.x86_64
(@koji-override-0/$releasever)
gcc-c++ = 4.6.2-1.fc16
Updated By: gcc-c++-4.6.3-2.fc16.x86_64 (updates)
gcc-c++ = 4.6.3-2.fc16
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

les wrote:

> Error: Package: clang-2.9-6.fc16.x86_64 (@updates)
> Requires: gcc-c++ = 4.6.2
> Removing: gcc-c++-4.6.2-1.fc16.x86_64
> (@koji-override-0/$releasever)
> gcc-c++ = 4.6.2-1.fc16
> Updated By: gcc-c++-4.6.3-2.fc16.x86_64 (updates)
> gcc-c++ = 4.6.3-2.fc16
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest


Either remove clang
$ yum remove clang

or update to llvm from updates-testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-4574
$ yum --enablerepo=updates-testing update clang

or... looks like llvm-2.9-9.fc16 is queue'd for stable now, so you could
just wait a day or 2.

-- rex

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

les wrote:
> HI, everyone,
> I am still having the update issue with gcc. I will follow this message
> with the error received from "yum update".
>
> Also my processor is periodically locking up. Is anyone else
> experiencing either of these errors? When it locks up, it is running
> one of the cores at or near 100%, and the dbus daemon is running at 54%,
> and if I click the x box on system monitor, the window remains open, but
> the process appears to have died.
>
> I am trying to figure out if these are related or separate issues that
> I have to resolve.

They would be different issues.

You’re not too clear on how much is locking up. Can you move the mouse
pointer when the error happens? Can you ping the machine across the
network?

> Can anyone offer any guidance, and as to the update of gcc, there was
> an earlier email where someone indicated that a update was needed but
> not available yet. Any help on that front either?

For what it’s worth, I can see much the same thing here. If you’re happy
to run with a version of clang and llvm that LLVM have released but is
still in Fedora testing, run
yum --enablerepo=updates-testing update clang
then try installing the gcc packages.

Hope this helps,

James.

--
E-mail: james@ | "I would like to apologise to the relatives of the fan
aprilcottage.co.uk | who gave me 29 books to sign in Odyssey 7, Manchester.
| I'm a little twitchy towards the end of a day of signing
| and did not mean to kill and eat him." -- Terry Pratchett
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org