From: William Stearns <wstearns@pobox.com>
To: Jeff Dike <jdike@addtoit.com>,
ML-uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Cc: William Stearns <wstearns@pobox.com>
Subject: [uml-devel] 2.6.16-rc1-um20060118 tls compile problem
Date: Wed, 18 Jan 2006 20:46:07 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601182042120.4057@sparrow> (raw)
Good evening, Jeff,
This is with your quilt set from today.
CC arch/um/os-Linux/tls.o
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'
arch/um/os-Linux/tls.c:48: warning: function declaration isn't a prototype
arch/um/os-Linux/tls.c:48: warning: data definition has no type or storage
class
arch/um/os-Linux/tls.c:49: error: syntax error before 'set_thread_area'
arch/um/os-Linux/tls.c:49: warning: type defaults to 'int' in declaration
of '_syscall1'
arch/um/os-Linux/tls.c:49: warning: function declaration isn't a prototype
arch/um/os-Linux/tls.c:49: warning: data definition has no type or storage
class
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
arch/um/os-Linux/tls.c: In function 'do_set_thread_area_tt':
arch/um/os-Linux/tls.c:55: warning: implicit declaration of function
'set_thread_area'
arch/um/os-Linux/tls.c: At top level:
arch/um/os-Linux/tls.c:62: warning: 'struct modify_ldt_t' declared inside
parameter list
arch/um/os-Linux/tls.c: In function 'do_get_thread_area_tt':
arch/um/os-Linux/tls.c:66: warning: implicit declaration of function
'get_thread_area'
make[1]: *** [arch/um/os-Linux/tls.o] Error 1
make: *** [arch/um/os-Linux] Error 2
[root@sparrow ~]# rpm -q gcc glibc-devel glibc-kernheaders
gcc-4.0.2-8.fc4
glibc-devel-2.3.5-10.3
glibc-kernheaders-2.4-9.1.94
Please let me know if there's more I can provide or try. Thanks
for all your work on this.
Cheers,
- Bill
---------------------------------------------------------------------------
Do you smoke after sex?
Why, do you know, I've never looked!
(Courtesy of Matthias Urlichs <smurf@noris.de>)
--------------------------------------------------------------------------
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
next reply other threads:[~2006-01-19 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 1:46 William Stearns [this message]
2006-01-19 4:13 ` [uml-devel] 2.6.16-rc1-um20060118 tls compile problem Jeff Dike
2006-01-20 3:00 ` William Stearns
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.0601182042120.4057@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