From: Srinivas Maturi <srinivas.maturi@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen-unstable build failure with c/s 19150
Date: Wed, 04 Feb 2009 15:14:19 -0800 [thread overview]
Message-ID: <498A214B.2030301@oracle.com> (raw)
In-Reply-To: <C5AFBAA4.C0E%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> Can you please try the attached patch?
>
> If that fails I'll have to not discard the .exit.* sections at link time.
>
Build succeeded with the patch.
Thanks,
Maturi
>
> On 04/02/2009 20:43, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
>
>
>> Oh, actually it's due to c/s 19148 I think, and probably due to using gcc
>> 3.3+. I can fix that...
>>
>> -- Keir
>>
>> On 04/02/2009 20:33, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
>>
>>
>>> It probably has something to do with changeset 19146. However, that's not
>>> guaranteed, and the build system appears to have been modified in your given
>>> example. For example CFLAGS is huge and contains many duplicates. Unless you
>>> can repro on a clean clone of xen-unstable you'll have to dig into it
>>> yourself.
>>>
>>> -- Keir
>>>
>>> On 04/02/2009 19:04, "Srinivas Maturi" <srinivas.maturi@oracle.com> wrote:
>>>
>>>
>>>> xen-unstable c/s 19150 failed to build for 64bit with the following
>>>> messages.
>>>>
>>>> Thanks,
>>>> Maturi
>>>>
>>>>
>>>> make[4]: Entering directory
>>>> `/builddir/build/BUILD/xen-unstable/xen/arch/x86'
>>>> gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>>>> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -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 -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 -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 -nostdinc -fno-builtin
>>>> -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include/asm-x86/mach-generic
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include/asm-x86/mach-default
>>>> -msoft-float -fno-stack-protector -mno-red-zone -fpic
>>>> -fno-reorder-blocks -fno-asynchronous-unwind-tables
>>>> -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -DVERBOSE -DCRASH_DEBUG
>>>> -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF .xen.d -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 -nostdinc -fno-builtin
>>>> -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include/asm-x86/mach-generic
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include/asm-x86/mach-default
>>>> -msoft-float -fno-stack-protector -mno-red-zone -fpic
>>>> -fno-reorder-blocks -fno-asynchronous-unwind-tables
>>>> -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -DVERBOSE -DCRASH_DEBUG
>>>> -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF .xen-syms.d -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 -nostdinc -fno-builtin
>>>> -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include/asm-x86/mach-generic
>>>> -I/builddir/build/BUILD/xen-unstable/xen/include/asm-x86/mach-default
>>>> -msoft-float -fno-stack-protector -mno-red-zone -fpic
>>>> -fno-reorder-blocks -fno-asynchronous-unwind-tables
>>>> -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -DVERBOSE -DCRASH_DEBUG
>>>> -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD -MF
>>>> .symbols-dummy.o.d -c
>>>> /builddir/build/BUILD/xen-unstable/xen/common/symbols-dummy.c -o
>>>> /builddir/build/BUILD/xen-unstable/xen/common/symbols-dummy.o
>>>> make[4]: Leaving directory `/builddir/build/BUILD/xen-unstable/xen/arch/x86'
>>>> ld -melf_x86_64 -T xen.lds -N
>>>> /builddir/build/BUILD/xen-unstable/xen/arch/x86/boot/built_in.o
>>>> /builddir/build/BUILD/xen-unstable/xen/common/built_in.o
>>>> /builddir/build/BUILD/xen-unstable/xen/drivers/built_in.o
>>>> /builddir/build/BUILD/xen-unstable/xen/xsm/built_in.o
>>>> /builddir/build/BUILD/xen-unstable/xen/arch/x86/built_in.o \
>>>> /builddir/build/BUILD/xen-unstable/xen/common/symbols-dummy.o -o
>>>> /builddir/build/BUILD/xen-unstable/xen/.xen-syms.0
>>>> /builddir/build/BUILD/xen-unstable/xen/drivers/built_in.o:(.eh_frame+0x9c0):
>>>> relocation truncated to fit: R_X86_64_PC32 against `.exit.text'
>>>> /builddir/build/BUILD/xen-unstable/xen/drivers/built_in.o:(.eh_frame+0xb08):
>>>> relocation truncated to fit: R_X86_64_PC32 against `.exit.text'
>>>> /builddir/build/BUILD/xen-unstable/xen/drivers/built_in.o:(.eh_frame+0xb28):
>>>> relocation truncated to fit: R_X86_64_PC32 against `.exit.text'
>>>> /builddir/build/BUILD/xen-unstable/xen/drivers/built_in.o:(.eh_frame+0xb48):
>>>> relocation truncated to fit: R_X86_64_PC32 against `.exit.text'
>>>> make[3]: *** [/builddir/build/BUILD/xen-unstable/xen/xen-syms] Error 1
>>>> make[3]: Leaving directory `/builddir/build/BUILD/xen-unstable/xen/arch/x86'
>>>> make[2]: *** [/builddir/build/BUILD/xen-unstable/xen/xen] Error 2
>>>> make[2]: Leaving directory `/builddir/build/BUILD/xen-unstable/xen'
>>>> make[1]: *** [install] Error 2
>>>> make[1]: Leaving directory `/builddir/build/BUILD/xen-unstable/xen'
>>>> make: *** [install-xen] Error 2
>>>> error: Bad exit status from /var/tmp/rpm-tmp.64030 (%build)
>>>>
>>>>
>>>>
>>>>
next prev parent reply other threads:[~2009-02-04 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 19:04 xen-unstable build failure with c/s 19150 Srinivas Maturi
2009-02-04 20:33 ` Keir Fraser
2009-02-04 20:43 ` Keir Fraser
2009-02-04 21:35 ` Keir Fraser
2009-02-04 23:14 ` Srinivas Maturi [this message]
2009-02-05 8:28 ` Keir Fraser
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=498A214B.2030301@oracle.com \
--to=srinivas.maturi@oracle.com \
--cc=keir.fraser@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.