From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33625 invoked by alias); 30 Jan 2019 19:45:44 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 31813 invoked by uid 89); 30 Jan 2019 19:45:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=BAYES_50,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=apt, ptrace_type_ret, D*ca, PTRACE_TYPE_RET X-HELO: mail-pf1-f179.google.com Received: from mail-pf1-f179.google.com (HELO mail-pf1-f179.google.com) (209.85.210.179) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 30 Jan 2019 19:45:40 +0000 Received: by mail-pf1-f179.google.com with SMTP id r136so297583pfc.6 for ; Wed, 30 Jan 2019 11:45:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=4V1pH/piO3NOd1fm0/6JlWb7XTO0tRsalXCZMcA8rs0=; b=qh636KiRv7B5dsoLhBda089xFwfY4WipjJVQXjtpgWg9qEzyMkFF3joI5/0dDYmLM3 Ldly3vm8kkNC6BX9bi6lEhdxnCJFL8byrrfcnMT3DJXsWHd4RuEPpY2uVfOcGPseq9K/ feuQ+k1461Nq7yDpXYogx12pmoWglDhVZhx+OxmtSg5Aykw+V3othC4E1lm4l+QsWV9O IZv+4hXELlSvtTab6AlRbtr6DStXwkt6WcOkxI9kgMoaqdxS+613uQWMZOMZfdQF+W5y aVQPm/2l8eOni3zLZSAHJYwfMKEGqqLjf01or6xOEmSsHtMcd/sumYjyCAdSb0UWIbGU IeWQ== MIME-Version: 1.0 References: <35b21a4d59530644ce75e76fb8be8bbd@polymtl.ca> In-Reply-To: From: =?UTF-8?Q?=C3=96mer_Sinan_A=C4=9Facan?= Date: Wed, 30 Jan 2019 19:45:00 -0000 Message-ID: Subject: Re: Buildling gdb on Ubuntu 18.04 To: Simon Marchi Cc: gdb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-SW-Source: 2019-01/txt/msg00043.txt.bz2 Interesting, I was also able to build in a docker container and it works wh= en I copy the executable to the host system, so my problem is kind of solved. I'm still wondering what's wrong with my system though ... (Too bad the bug exists in the development version too so I have to deal wi= th it in my application...) =C3=96mer Simon Marchi , 30 Oca 2019 =C3=87ar, 18:50 tarihinde =C5=9Funu yazd=C4=B1: > > On 2019-01-30 10:12, =C3=96mer Sinan A=C4=9Facan 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