linux-um archives
 help / color / mirror / Atom feed
From: William Stearns <wstearns@pobox.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: ML-uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] 2.6.16-rc1-um20060118 tls compile problem
Date: Thu, 19 Jan 2006 22:00:13 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601192143270.3892@sparrow> (raw)
In-Reply-To: <20060119041342.GA8265@ccure.user-mode-linux.org>

Good evening, Jeff,

On Wed, 18 Jan 2006, Jeff Dike wrote:

> On Wed, Jan 18, 2006 at 08:46:07PM -0500, William Stearns wrote:
>> arch/um/os-Linux/tls.c:48: error: syntax error before 'get_thread_area'
>> arch/um/os-Linux/tls.c:48: warning: type defaults to 'int' in declaration
>> of '_syscall1'
>
> Can you try this patch for this one?
>
> Index: linux-2.6.15/arch/um/os-Linux/tls.c
> ===================================================================
> --- linux-2.6.15.orig/arch/um/os-Linux/tls.c    2006-01-18 13:40:01.000000000 -0500
> +++ linux-2.6.15/arch/um/os-Linux/tls.c 2006-01-18 22:18:57.000000000 -0500
> @@ -1,5 +1,6 @@
> #include <errno.h>
> #include <sys/ptrace.h>
> +#include <linux/unistd.h>
> #include <asm/ldt.h>
> #include "uml-config.h"

 	That patch helped.

>> arch/um/os-Linux/tls.c:51: warning: 'struct modify_ldt_t' declared inside
>> parameter list
>> arch/um/os-Linux/tls.c:51: warning: its scope is only this definition or
>> declaration, which is probably not what you want
>
> For these, try backing out the user-desc patch.  You may one of those
> primitive beings who lacks a modify_ldt_t in your asm/ldt.h.

 	Actually I don't need to revert this one; after reverting the 
compile fails.  Leaving it in works.  The compile finishes.
 	Thanks again for your help, Jeff and Blaisor.
 	Cheers,
 	- Bill

---------------------------------------------------------------------------
 	"Microsoft's biggest and most dangerous contribution to the
software industry may be the degree to which it has lowered user
expectations."
 	-- Esther Schindler, OS/2 Magazine
(Courtesy of Bob Tracy - TDS <rct@merkin.csap.af.mil>)
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com).  Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at:   http://www.stearns.org
--------------------------------------------------------------------------


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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:[~2006-01-20  3:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19  1:46 [uml-devel] 2.6.16-rc1-um20060118 tls compile problem William Stearns
2006-01-19  4:13 ` Jeff Dike
2006-01-20  3:00   ` William Stearns [this message]

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=Pine.LNX.4.64.0601192143270.3892@sparrow \
    --to=wstearns@pobox.com \
    --cc=jdike@addtoit.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