Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: "Ömer Sinan Ağacan" <omeragacan@gmail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Buildling gdb on Ubuntu 18.04
Date: Wed, 30 Jan 2019 15:50:00 -0000	[thread overview]
Message-ID: <f492526c8f994d13bba52ee47f2cef5e@polymtl.ca> (raw)
In-Reply-To: <CAMQQO3kS1pOmgpAjBgrwLdjv7fhaim+WOjTFg9CffUAgz5fBow@mail.gmail.com>

On 2019-01-30 10:12, Ömer Sinan Ağacan wrote:
> Actually it's not undefined, I see this in the file
> 
>     /* Define as the return type of ptrace. */
>     #define PTRACE_TYPE_RET long
> 
> Do I need to include config.h in a file maybe?

config.h should already be included wherever necessary.  I am a bit at 
loss here.  GDB should build fine using these standard steps in most 
situations:


git clone git://sourceware.org/git/binutils-gdb.git
cd binutils-gdb
./configure
make


I just tried these commands in an Ubuntu 18.04 Docker container, and it 
built fine.  Note that to make sure to have all necessary dependencies 
required to build GDB, you can use "apt-get build-dep gdb" on 
Debian/Ubuntu (to be able to use "build-dep" in a docker container, you 
need to uncomment the "deb-src" lines in /etc/apt/sources.list and do an 
"apt-get update").  The versions of all the build tools in Ubuntu 18.04 
are expected to work, so there should be no need to build bison or 
anything from source.

Simon


  reply	other threads:[~2019-01-30 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  7:41 Ömer Sinan Ağacan
2019-01-30 14:58 ` Simon Marchi
2019-01-30 15:12   ` Ömer Sinan Ağacan
2019-01-30 15:50     ` Simon Marchi [this message]
2019-01-30 19:45       ` Ömer Sinan Ağacan
2019-01-30 20:01         ` Simon Marchi
2019-01-31  6:23           ` Ömer Sinan Ağacan
2019-01-31 15:54             ` Simon Marchi

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=f492526c8f994d13bba52ee47f2cef5e@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb@sourceware.org \
    --cc=omeragacan@gmail.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