From: Nathan March <nathan@gt.net>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen 4.1.0 RC2 released,
Date: Mon, 31 Jan 2011 10:14:38 -0800 [thread overview]
Message-ID: <4D46FC0E.6060102@gt.net> (raw)
In-Reply-To: <1296297936.20804.123.camel@localhost.localdomain>
On 1/29/2011 2:45 AM, Ian Campbell wrote:
> I just built Xen with the following patch and it didn't break on a
> Debian system (i.e. without as-needed enabled by default). Can you try
> it in your environment?
Initially failed with:
ld -Wl,--no-as-needed -melf_x86_64 -r -o built_in.o head.o
ld: unrecognized option '-Wl,--no-as-needed'
ld: use the --help option for usage information
Adjusted the patch to have a space instead of a comma between params and
I get:
gcc -D__ASSEMBLY__ -O1 -fno-omit-frame-pointer
-fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -Wall
-Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement
-nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix
include -Werror -Wno-pointer-arith -pipe
-I/var/home/xen41/xen-unstable.hg/xen/include
-I/var/home/xen41/xen-unstable.hg/xen/include/asm-x86/mach-generic
-I/var/home/xen41/xen-unstable.hg/xen/include/asm-x86/mach-default
-msoft-float -fno-stack-protector -fno-exceptions -mno-red-zone -fpic
-fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g
-D__XEN__ -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD
-MF .head.o.d -c head.S -o head.o
ld -Wl --no-as-needed -melf_x86_64 -r -o built_in.o head.o
ld: unrecognized option '-Wl'
ld: use the --help option for usage information
xen5 xen-unstable.hg # ld -v
GNU ld (GNU Binutils) 2.19.1
If I drop the -Wl out, it bails on:
gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g
-fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes
-Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD
-MF .xen-tmem-list-parse.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-Werror -I ../../tools/python/xen/lowlevel/xc -I ../../tools/libxc -I
../../tools/include --no-as-needed xen-tmem-list-parse.c -o
xen-tmem-list-parse
cc1: error: unrecognized command line option "-fno-as-needed"
the --no-as-needed is valid for ld according to the man, but not for gcc
as far as I can see.
- Nathan
next prev parent reply other threads:[~2011-01-31 18:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 23:05 Xen 4.1.0 RC2 released, Nathan March
2011-01-28 8:53 ` Ian Campbell
2011-01-28 19:09 ` Nathan March
2011-01-28 19:12 ` Ian Campbell
2011-01-28 19:22 ` Nathan March
2011-01-28 19:36 ` Ian Campbell
2011-01-28 21:19 ` Nathan March
2011-01-28 21:54 ` Ian Campbell
2011-01-28 22:24 ` Nathan March
2011-01-29 10:45 ` Ian Campbell
2011-01-31 18:14 ` Nathan March [this message]
2011-01-31 19:30 ` Ian Campbell
2011-01-31 19:54 ` Nathan March
2011-02-01 18:51 ` Ian Jackson
2011-02-01 18:53 ` Ian Campbell
2011-03-21 14:43 ` Ian Campbell
2011-04-01 17:38 ` Nathan March
2011-04-01 18:35 ` Ian Campbell
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=4D46FC0E.6060102@gt.net \
--to=nathan@gt.net \
--cc=Ian.Campbell@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).