Re: [Xen-devel] xen-unstable build failure with c/s 19150

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

Can you please try the attached patch?

If that fails I'll have to not discard the .exit.* sections at link time.

 -- Keir

On 04/02/2009 20:43, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx> 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@xxxxxxxxxx> 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)
>>> 
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

link.patch
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel