qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Charpentier <charpent@bacbuc.dyndns.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Debian blues (Re: Problem compiling with gcc 3.3 on 2.6.14 (Debian))
Date: Tue, 29 Nov 2005 22:07:52 +0100	[thread overview]
Message-ID: <dmifv9$lpa$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0511291158050.13263@gauss.mandriva.com>

Gwenole Beauchesne wrote:
> Hi,
> 
> 
>>Case in point : I distinctly reember reading a convoluted thread in one 
>>of the Debian lists about this /etc/alternative issue for gcc... Was I 
>>drunk ? Or what ?
> 
> 
> I don't know what all this rant is about

The idiocy of having a system perfectly able to handle alternative 
packages ... except when it isn't, for reasons too obscure to be 
understood by a 31-year computer user (yes, I wrote my first Fortran 
program in 1974..) when he isnt a dedicated system maintainer. I *use* 
computers, dammit, I have not too much time to play system administrator....

>                                          but it's always best to keep the 
> system compiler as chosen by the distributor.

That's exactly what I was trying to do. Debian has switched to GCC 4 for 
kernels. But (parts of) QEMU) need gcc 3.4. Hence the raindance..

>                                                If you want to use 
> alternatives, use CC overrides or other configure option.

I missed the doc-"howto" for these options. Last time I tried, I ended 
up with "Incorrect module format" errores and/or bad compilations 
errors. I gave up and learned to change compilers...

>>If you can suggest a more steamlined way, I'd be happy to hear from it, 
>>and even more happy to read it on Fabrice's pages or somewhere in the 
>>documentation...
> 
> 
> Use DKMS for kqemu modules?

No such thing on Debian. They have a (supposedly) nice system 
("module-assistant") for compilong out-of-tree modules... which I never 
quite figured out. When I need an out-oft-tree kernel (which is rare 
nowadays), I still roll my own kernel, à la Neanderthal...

					Emmanuel Charpentier

  parent reply	other threads:[~2005-11-29 21:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28  8:46 [Qemu-devel] Problem compiling with gcc 3.3 on 2.6.14 (Debian) Emmanuel Charpentier
2005-11-28 16:59 ` Jim C. Brown
2005-11-28 19:41   ` Natalia Portillo
2005-11-28 21:24     ` [Qemu-devel] Debian blues (Re: Problem compiling with gcc 3.3 on 2.6.14 (Debian)) Emmanuel Charpentier
2005-11-28 22:35       ` Daniel Jacobowitz
2005-11-29  8:58         ` [Qemu-devel] " Emmanuel Charpentier
2005-11-29 11:00           ` Gwenole Beauchesne
2005-11-29 14:02             ` carlo.andreoli
2005-11-29 22:41               ` Pascal Terjan
2005-11-30  8:13                 ` carlo.andreoli
2005-11-29 21:07             ` Emmanuel Charpentier [this message]
2005-11-28 21:09   ` [Qemu-devel] Re: Problem compiling with gcc 3.3 on 2.6.14 (Debian) Emmanuel Charpentier
2005-11-28 22:27   ` Emmanuel Charpentier
2005-11-29  1:06     ` Brad Watson
2005-11-29  1:07     ` Brad Watson
2005-11-29 10:32     ` Sylvain Petreolle
2005-11-29 21:09       ` Emmanuel Charpentier
2005-11-30  8:25         ` [Qemu-devel] Problem compiling with gcc 3.3 on 2.6.14 Jernej Simončič

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='dmifv9$lpa$1@sea.gmane.org' \
    --to=charpent@bacbuc.dyndns.org \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).