From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 76349 invoked by alias); 30 Jan 2019 15:12:54 -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 76341 invoked by uid 89); 30 Jan 2019 15:12:54 -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=Kernel, IRC, osa1, sk:4548c5b X-HELO: mail-pl1-f179.google.com Received: from mail-pl1-f179.google.com (HELO mail-pl1-f179.google.com) (209.85.214.179) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 30 Jan 2019 15:12:52 +0000 Received: by mail-pl1-f179.google.com with SMTP id z23so11184671plo.0 for ; Wed, 30 Jan 2019 07:12:52 -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=3at68zEdH4lj/WcT5VOzInqy3fkWRw7Xdz32bKy5ZJI=; b=m6ZMj1H2nBI09bCK889SVlWiwT/prbzBMIcWRgLVzoPtCquuckydjYegY9xqOwagCK p5/BWZBqKvwZ8my16Lxi8Xr9SsBu3tRk6gW7XlqEOGe869SJqkb124nlUxJZmA5pYeew vR6wIli3Zf4NyLD/rtE/6x6Bd095y885iecurQgkE52LpvBA9wPt6/M+4AAZA14XeGjV b/Uw22BzTRlIYKnJ6JYhxFhg1BaTURO/9tAZahNW493AJKUViwBOL9fRMBKk2FUVtf7S 7wR/W3g2crcGxXW8K5B9QVIL05o+aBL1pMK5lZaOZVYqtdt3rOSR7stLpkKBEpssIMIG Cz/Q== MIME-Version: 1.0 References: <35b21a4d59530644ce75e76fb8be8bbd@polymtl.ca> In-Reply-To: <35b21a4d59530644ce75e76fb8be8bbd@polymtl.ca> From: =?UTF-8?Q?=C3=96mer_Sinan_A=C4=9Facan?= Date: Wed, 30 Jan 2019 15:12: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/msg00041.txt.bz2 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? =C3=96mer Simon Marchi , 30 Oca 2019 =C3=87ar, 17:58 tarihinde =C5=9Funu yazd=C4=B1: > > On 2019-01-30 02:40, =C3=96mer Sinan A=C4=9Facan wrote: > > I'm trying to build gdb from git on Ubuntu 18.04 to see if some of the > > bugs I'm > > observing with machine interface of 8.1.0.20180409-git are fixed in the > > development version. I got a few different errors before but with some > > help from > > people on the IRC channel I was able to make progress, and current > > status is > > this: https://gist.github.com/osa1/4548c5bc2d167541557e0a349944eb00 > > > > Does anyone have any ideas on how to move from there? Kernel version on > > Ubuntu > > 18.04: 4.15.0-44-generic > > > > Thanks > > > > =C3=96mer > > About this error: > > nat/gdb_ptrace.h:129:8: error: =E2=80=98PTRACE_TYPE_RET=E2=80=99 does not= name a type; > did you mean =E2=80=98PTRACE_TYPE_ARG3=E2=80=99? > > The PTRACE_TYPE_RET type should be defined in the gdb/config.h file, in > your build directory. For example, I have > > 650 /* Define as the return type of ptrace. */ > =E2=94=82warning: File > "/home/emaisin/build/binutils-gdb/gdb/gdb-gdb.py" auto-loading has be > 651 #define PTRACE_TYPE_RET long > > > Is there a mention of PTRACE_TYPE_RET in your config.h? I assume it is > undefined? > > Simon