From: Vincent Diepeveen <diep@xs4all.nl>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC 4.7 build problems
Date: Sun, 15 Apr 2012 22:24:00 -0000 [thread overview]
Message-ID: <6C72E21C-BAB1-4B02-A1A7-39C675EC38C9@xs4all.nl> (raw)
In-Reply-To: <CAH6eHdRrH26JfWR7MAO8MjmDiVhEYL1T-75cRedsy6bVAtQneA@mail.gmail.com>
hi,
It's not possible to install any of the packages glibc-* from
ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/i386/os/
Packages
basically it says each time in so many words the package manager that
there is a conflict between the same packages i686 and x64,
as of course i'm x64 here.
Is there a way to compile GCC in a manner it doesn't need stubs-32.h,
as i'm 64 bits here?
Can i compile gcc x64 only somehow?
Would it help if i kick out Java?
In http://gcc.gnu.org/install/configure.html i'm looking there but
don't know which one to use.
On Apr 16, 2012, at 12:03 AM, Jonathan Wakely wrote:
> On 15 April 2012 22:59, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>> On 15 April 2012 22:52, Vincent Diepeveen <diep@xs4all.nl> wrote:
>>> Thanks Jonathan!
>>>
>>> Google gave me how to add the DVD-rom to the repository, it's
>>> indexing the
>>> 4428 rpm's there now
>>> from the i386 dvd1 of Scientific Linux
>>>
>>> Hope it installs the glibc-devel.i868 then and that this solves
>>> the problem!
>>
>> If you don't want to wait you could just grab that RPM, either from
>> the DVD or the internet, with
>> wget ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/
>> i386/updates/security/glibc-devel-2.12-1.47.el6_2.9.i686.rpm
>
> Actually to match your existing 64-bit glibc I think that should be
>
> wget ftp://mirror.switch.ch/pool/1/mirror/scientificlinux/6rolling/
> i386/os/Packages/glibc-2.12-1.47.el6.i686.rpm
>
>> then install it with
>> yum localinstall glibc-devel-2.12-1.47.el6_2.9.i686.rpm
next prev parent reply other threads:[~2012-04-15 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171979E8-3362-4C94-B69A-2757BF6BB24B@xs4all.nl>
[not found] ` <alpine.DEB.2.02.1204151834250.2580@laptop-mg.saclay.inria.fr>
2012-04-15 20:29 ` Vincent Diepeveen
2012-04-15 20:46 ` Marc Glisse
2012-04-15 21:00 ` Jonathan Wakely
2012-04-15 21:10 ` Vincent Diepeveen
2012-04-15 21:13 ` Jonathan Wakely
2012-04-15 21:15 ` Jonathan Wakely
2012-04-15 21:52 ` Vincent Diepeveen
2012-04-15 22:00 ` Jonathan Wakely
2012-04-15 22:03 ` Jonathan Wakely
2012-04-15 22:24 ` Vincent Diepeveen [this message]
2012-04-15 23:19 ` Jonathan Wakely
2012-04-15 23:37 ` Vincent Diepeveen
2012-04-16 0:25 ` Vincent Diepeveen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6C72E21C-BAB1-4B02-A1A7-39C675EC38C9@xs4all.nl \
--to=diep@xs4all.nl \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).