qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFT PATCH v2] configure: Simplify alternate .text segm


From: Richard Henderson
Subject: Re: [Qemu-devel] [RFT PATCH v2] configure: Simplify alternate .text segment
Date: Fri, 21 Jun 2013 11:37:10 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6

On 06/20/2013 06:15 AM, Ed Maste wrote:
> +    try_ldflags="-Ttext-segment=$textseg_addr"

Two problems: (1) you forgot "-Wl," here.
(2) We're running into some strange problem with git submodule init dtc.

>From config.log:

> cc -Werror -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
> -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings 
> -Wmissing-prototypes -fno-strict-aliasing -Wendif-labels 
> -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security 
> -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration 
> -Wold-style-definition -Wtype-limits -fstack-protector-all 
> -I/usr/include/libpng15 -I/usr/include/spice-server -I/usr/include/cacard 
> -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/nss3 -I/usr/include/nspr4 -I/usr/include/spice-1 
> -I/usr/include/nss3 -I/usr/include/nspr4 -pthread -I/usr/include/glib-2.0 
> -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 
> -I$(SRC_PATH)/dtc/libfdt -o /tmp/qemu-conf-29328-15251-22199.exe 
> /tmp/qemu-conf-7372-15251-10868.c -Wl,--warn-common -m64 -g 
> -Wl,-Ttext-segment=0x60000000
> cc1: error: $(SRC_PATH)/dtc/libfdt: No such file or directory [-Werror]
> cc1: all warnings being treated as errors

And because of that -Werror, we never detect that -Ttext-segment is supported,
which leads to the incorrect frobbing of the config-host.ld:

>   PROVIDE (__executable_start = 0x60000000SEGMENT_START("text-segment", 
> 0x400000)); . = SEGMENT_START("text-segment", 0x400000) + SIZEOF_HEADERS;

I have no idea what's going wrong with the libfdt thing...


r~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]