From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>,
Pedro Alves <palves@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: 32-bit buildbot builders broken [Re: Your commit 'Build GDB as a C++ program by default' broke GDB]
Date: Wed, 27 Apr 2016 19:54:00 -0000 [thread overview]
Message-ID: <wwok1t5q25fm.fsf@ericsson.com> (raw)
In-Reply-To: <87potalu46.fsf@redhat.com>
Sergio Durigan Junior writes:
> On Wednesday, April 27 2016, Antoine Tremblay wrote:
>
>> Sergio Durigan Junior writes:
>>
>>> On Thursday, April 21 2016, Pedro Alves wrote:
>>>
>>>>> g++ -g -O2 -I. -I../../binutils-gdb/gdb -I../../binutils-gdb/gdb/common
>>>>> -I../../binutils-gdb/gdb/config
>>>> ...
>>>>> -I../../binutils-gdb/gdb/../libdecnumber
>>>>> -I../../binutils-gdb/gdb/gnulib/import -Ibuild-gnulib/import -DTUI=1
>>>>> -I/usr/include/python2.7 -I/usr/include/python2.7 -Wall
>>>>> -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function
>>>>> -Wno-switch -Wno-char-subscripts -Wempty-body -Wno-sign-compare
>>>>> -Wno-write-strings -Wno-narrowing -Wformat-nonliteral -Werror -c -o
>>>>> linux-thread-db.o -MT linux-thread-db.o -MMD -MP -MF
>>>>> .deps/linux-thread-db.Tpo ../../binutils-gdb/gdb/linux-thread-db.c
>>>>> In file included from ../../binutils-gdb/gdb/i386-linux-nat.c:25:0:
>>>>> ../../binutils-gdb/gdb/i386-linux-nat.c: In function void fetch_regs(regcache*, int):
>>>>> ../../binutils-gdb/gdb/i386-linux-nat.c:207:46: error: cast from elf_greg_t (*)[27] {aka long long unsigned int (*)[27]} to int loses precision [-fpermissive]
>>>>> if (ptrace (PTRACE_GETREGS, tid, 0, (int) ®s) < 0)
>>>>
>>>>
>>>> ... however this error is exactly what you get if you compile with a
>>>> 64-bit compiler, and forget to pass -m32 to gcc/g++. IOW,
>>>> it compiles i386-linux-nat.c as if for a 64-bit host, which fails.
>>>>
>>>> So I suspect the builder is using CC="gcc -m32", and now that a C++ compiler
>>>> is involved, it needs to be updated to pass CXX="g++ -m32" as well.
>>>
>>> Yeah, actually I was setting CFLAGS without setting CXXFLAGS for these
>>> builders, so I fixed that now. Thanks for letting me know, and sorry
>>> about that.
>>
>> I was looking at
>> http://gdb-build.sergiodj.net/builders/Fedora-x86_64-m32/builds/3499/steps/configure%20gdb/logs/stdio
>>
>> And it seems it builds in 64 bit, there's no --host=i386... or -m32 ?
>
> Hey Antoine,
>
> Thanks for the message. So, as I said on IRC, the purpose of this
> builder is to perform a 64-bit compilation of GDB (i.e., without -m32),
> but run the testsuite on 32-bit mode (i.e., passing
> --target_board=unix/-m32 to runtest).
>
> Maybe the builder's name is confusing, and I apologize for that. I
> could try to add a better description of it on the page.
>
Hehe yes thanks for the clarification, I was actually looking at an
example to build a 32bit gdb and I just clicked on the m32 tag...
Guess I went too fast there.
Thanks,
Antoine
prev parent reply other threads:[~2016-04-27 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1at1Am-0004GM-6R@kwanyin.sergiodj.net>
2016-04-21 9:09 ` Pedro Alves
2016-04-21 20:56 ` Sergio Durigan Junior
2016-04-27 19:06 ` Antoine Tremblay
2016-04-27 19:39 ` Sergio Durigan Junior
2016-04-27 19:54 ` Antoine Tremblay [this message]
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=wwok1t5q25fm.fsf@ericsson.com \
--to=antoine.tremblay@ericsson.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.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