linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Quantum Skyline <quantum.skyline@gmail.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] __attribute_used__ error on 2.6.23.9
Date: Wed, 26 Dec 2007 14:26:09 -0800	[thread overview]
Message-ID: <4772D501.6050306@gmail.com> (raw)

Hi,

I've been trying to modify the UML makefiles in the 2.6.23.9 kernel to 
compile against a different C library, but I'm running into trouble 
getting parts of UML to compile with GCC 4.2.1.  In particular, files in 
os-Linux that use functions like __uml_setup are causing GCC to throw 
errors.

For example, when I try to compile arch/um/os-Linux/aio.c in my 
environment, I get the following:

gcc-4.2.1-rev -Wp,-MD,arch/um/os-Linux/.aio.o.d  -Wall -Wundef 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common 
-Werror-implicit-function-declaration -Os -D__arch_um__ 
-DSUBARCH=\"i386\" -Dvmap=kernel_vmap 
-Din6addr_loopback=kernel_in6addr_loopback 
-Din6addr_any=kernel_in6addr_any -march=i686 
-mpreferred-stack-boundary=2 -ffreestanding -D_LARGEFILE64_SOURCE 
-fno-unit-at-a-time -fno-omit-frame-pointer -fno-optimize-sibling-calls 
-g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign 
-Iarch/um/include 
-I/home/tmjackso/build/orchestra/uml/linux-2.6.23.9/arch/um/include/skas 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-DHAVE_AIO_ABI -v -nostdinc -I../../dietlibc/trunk/include -isystem 
/usr/local/gcc-4.2.1-rev/include -c -o arch/um/os-Linux/aio.o 
arch/um/os-Linux/aio.c
arch/um/os-Linux/aio.c:307: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or 
‘__attribute__’ before ‘__attribute_used__’
arch/um/os-Linux/aio.c:307: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or 
‘__attribute__’ before ‘__attribute_used__’
arch/um/os-Linux/aio.c:350: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or 
‘__attribute__’ before ‘__attribute_used__’
arch/um/os-Linux/aio.c:360: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or 
‘__attribute__’ before ‘__attribute_used__’

I know that __uml_setup and friends are defined in 
arch/um/include/init.h and it is being included, but it seems like GCC 
is not using it.  If I comment out __uml_setup, other files which have 
functions starting with two underscores like __uml_initcall also cause 
compilation to fail.

Can anyone give some hints to solve this problem?

Cheers,

Todd Jackson

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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:[~2007-12-26 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 22:26 Quantum Skyline [this message]
2007-12-27  0:42 ` [uml-devel] __attribute_used__ error on 2.6.23.9 Jeff Dike
2007-12-27  2:30   ` Todd Jackson
2007-12-27  2:58     ` Jeff Dike
2008-01-02 15:37     ` 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=4772D501.6050306@gmail.com \
    --to=quantum.skyline@gmail.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;
as well as URLs for NNTP newsgroup(s).