Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: <sellcey@imgtec.com>
Cc: <jose.marchesi@oracle.com>, <gdb-patches@sourceware.org>
Subject: Re: Build failure with probe patch
Date: Thu, 19 Feb 2015 04:39:00 -0000	[thread overview]
Message-ID: <877fveqzuw.fsf@redhat.com> (raw)
In-Reply-To: <1424306916.27855.115.camel@ubuntu-sellcey> (Steve Ellcey's	message of "Wed, 18 Feb 2015 16:48:36 -0800")

On Wednesday, February 18 2015, Steve Ellcey wrote:

> I would like to avoid updating GCC if possible.  I build on old systems
> because some of our customers use old systems.  I don't know if gdb has
> a 'minimal GCC' that it can be compiled with like GCC and some other
> projects have.

Sure, it's your option.  I know some people here still use old compilers
to build GDB, but I don't remember of any explicit rule about a minimal
GCC version.

>  I tried changing the definition of 'dof' to be '
> bfd_byte *' instead of 'struct dtrace_dof_hdr *' and then casting it on
> the call to dtrace_process_dof instead of the call to
> bfd_malloc_and_get_section.  That got rid of the type punning message
> but I wound up seeing:
>
> /scratch/gcc/nightly/src/binutils-gdb/gdb/dtrace-probe.c: In function
> 'dtrace_get_probes':
> /scratch/gcc/nightly/src/binutils-gdb/gdb/dtrace-probe.c:64: warning:
> 'arg.expr' is used uninitialized in this function
> make[1]: *** [dtrace-probe.o] Error 1

This error message is completely misleading.  I built GCC 4.1.2 and
managed to reproduce it, but I couldn't find the reason.  Anyway, I have
not spent too much time on the problem, but let me know if you need some
help.

> Which I do not understand at all.  I will investigate some more and see
> if there is a clean way to get this to compile with GCC 4.1.2.

That would be much appreciated.  Thank you!

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2015-02-19  4:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 17:51 Steve Ellcey 
2015-02-18 23:58 ` Sergio Durigan Junior
2015-02-19  0:48   ` Steve Ellcey
2015-02-19  4:39     ` Sergio Durigan Junior [this message]
2015-02-19 15:55     ` Jose E. Marchesi
2015-02-19 16:53       ` Pedro Alves
2015-02-19 17:32         ` Jose E. Marchesi
2015-02-19 17:48           ` Steve Ellcey
2015-02-19 20:41             ` Jose E. Marchesi
2015-02-19 21:18               ` Sergio Durigan Junior
2015-02-19 21:48                 ` Steve Ellcey
2015-02-19 21:52                   ` Sergio Durigan Junior
2015-02-19 21:59                     ` Steve Ellcey
2015-02-19 18:30           ` Pedro Alves
2015-02-19 20:11             ` Jose E. Marchesi
2015-02-19 10:43   ` Pedro Alves

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=877fveqzuw.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=sellcey@imgtec.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