linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: David Shane Holden <dpejesh@yahoo.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] fix extern inline errors with gcc 4.3.0
Date: Tue, 15 Jul 2008 16:13:22 -0400	[thread overview]
Message-ID: <20080715201322.GA15836@c2.user-mode-linux.org> (raw)
In-Reply-To: <g5ir1u$14n$1@ger.gmane.org>

On Tue, Jul 15, 2008 at 11:42:05AM -0700, David Shane Holden wrote:
> Jeff Dike wrote:
> > On Mon, Jul 14, 2008 at 11:30:15AM -0700, David Shane Holden wrote:
> >> I tried to build a UML 2.6.26 kernel on Debian (32-bit) and ran into the 
> >> same problem reported here http://marc.info/?t=121011533500002&r=1&w=2. 
> > 
> > It's really 2.6.26, and not something from a day or two earlier?  I
> > fixed the compilation bugs, supposedly, just before 2.6.26.
> 
> Yeah, it's a vanilla 2.6.26, and when comparing it to 2.6.26-rc9 the 
> only difference in arch/um was the change for no-unit-at-a-time.

OK, I misunderstood - I thought you were saying you got compilation
errors, rather than crashes.  Hence my incredulity, since that patch
was supposed to fix the compile errors.

> > 
> >>   If I use gcc 4.3 everything works fine, but if I use gcc 4.1 or 4.2, 
> >> UML crashes on startup.
> > 
> > If the crash says ptrace in it, then I'm currently trying to figure
> > out what's happening with that.
> 
> It's crashing in wait_stub_done just like the poster of the message was 
> having, it appears gcc 4.1 and 4.2 need -fno-unit-at-a-time.

Well, we need to figure out why the initcalls aren't happening with
-unit-at-a-time and some versions of gcc.

		    	 	  Jeff

-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2008-07-15 20:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1214488251-20927-1-git-send-email-bhalevy@panasas.com>
2008-06-27 16:26 ` [uml-devel] [PATCH] fix extern inline errors with gcc 4.3.0 Jeff Dike
     [not found]   ` <7225594ED4A1304C9E43D030A886D221050BE1@daytona.int.panasas.com>
2008-06-29  7:32     ` [SPAM] " Benny Halevy
2008-06-30 16:22       ` Jeff Dike
2008-06-30 16:37         ` Benny Halevy
2008-07-07 16:58           ` Jeff Dike
2008-06-30 16:43         ` Adrian Bunk
2008-08-08  1:02         ` Rob Landley
2008-08-08  1:42         ` Rob Landley
2008-07-14 18:30 ` David Shane Holden
2008-07-15 16:24   ` Jeff Dike
2008-07-15 18:42     ` [SPAM] " David Shane Holden
2008-07-15 20:13       ` Jeff Dike [this message]
     [not found]         ` <487DDF69.9030801@panasas.com>
     [not found]           ` <487DE1B3.1060502@panasas.com>
2008-07-18 20:49             ` Jeff Dike

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=20080715201322.GA15836@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=dpejesh@yahoo.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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