mailing list of musl libc
 help / color / mirror / code / Atom feed
From: mzpqnxow <musl@mzpqnxow.com>
To: musl@lists.openwall.com
Cc: Rich Felker <dalias@libc.org>
Subject: Re: Issues building gdbserver with musl
Date: Sat, 03 Jun 2017 17:19:39 +0000	[thread overview]
Message-ID: <CA+qPFc+9dM9CtABhCFurO-X8L2GMKUu5-WEk0UkRxKQQkEZ5ZQ@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1soFtezHykBNmwJ=yeV6biquCdPi70jE9pzgsgX+pSoyKg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3070 bytes --]

Which version of gdb are you using? I've found I had to patch several
versions of gdb when building gdbserver for non-x86 platforms, possibly due
to less QA testing of these "obscure" platforms on the gdb dev side.

I at least encountered issues with ARM and MIPS on some of the 6 and/or 7
branch of gdb. Patches were only about 20-30 lines max.

I'm maintaining a collection of statically linked gdbserver executables[1]
for various embedded platforms so I'd be happy to write a patch to address
the issues in gdb and send them to you and upstream if they can be fixed on
the gdb side of things. I need to add those platforms anyway so it's no
bother.

I'll take a look today to see if I can patch any errors in gdb to get a
functional build but if it's in fact a musl issue I'll have to defer.

Have you had success building the same gdbserver versions with glibc or
uClibc for the same architectures?

Adam

1.
https://github.com/mzpqnxow/embedded-toolkit/tree/master/prebuilt_static_bins/gdbserver

On Sat, Jun 3, 2017 at 10:35 Khem Raj <raj.khem@gmail.com> wrote:

> Hi Thomas
>
>
>
> On Sat, Jun 3, 2017 at 7:14 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Hello,
> >
> > We are building a number of toolchains, some of them using the musl C
> > library, and are seeing that gdbserver fails to build with musl on a
> > number of architectures. We have used musl 1.1.16, i.e the latest
> > version.
> >
> > Here are the failures that we see:
> >
> >  - On SuperH:
> >
> >
> usr/sh4-buildroot-linux-musl/sysroot/usr/include/asm/ptrace_32.h:44:8:
> error: redefinition of 'struct pt_regs'
> >
> >  - On PowerPC64 and PowerPC64le:
> >
> >
> usr/powerpc64-buildroot-linux-musl/sysroot/usr/include/asm/ptrace.h:31:8:
> error: redefinition of 'struct pt_regs'
> >
> usr/powerpc64le-buildroot-linux-musl/sysroot/usr/include/asm/ptrace.h:31:8:
> error: redefinition of 'struct pt_regs'
> >
> >  - On PowerPC:
> >
> >
> usr/powerpc-buildroot-linux-musl/sysroot/usr/include/asm/ptrace.h:31:8:
> error: redefinition of 'struct pt_regs'
>
>
> for ppe issues you can use something like
>
> http://git.yoctoproject.org/clean/cgit.cgi/poky/tree/meta/recipes-devtools/gdb/gdb/0004-ppc-ptrace-Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch
>
> >
> >  - On Microblaze, little endian and big endian
> >
> >
> usr/microblaze-buildroot-linux-musl/sysroot/usr/include/sys/procfs.h:30:2:
> error: unknown type name 'elf_gregset_t'
> >    error: 'Elf64_auxv_t' undeclared (first use in this function)
> >    error: 'Elf32_auxv_t' undeclared (first use in this function)
> >    ...
> >
> > On all those architectures, gdbserver builds fine with other C libraries.
> >
> > I had a brief look at the commits in musl since 1.1.16 and couldn't
> > spot anything that looked related.
> >
> > Are you interested in fixing those issues? If needed, I can provide an
> > easy way of reproducing those build failures.
> >
> > Thanks!
> >
> > Thomas
> > --
> > Thomas Petazzoni, CTO, Free Electrons
> > Embedded Linux and Kernel engineering
> > http://free-electrons.com
>

[-- Attachment #2: Type: text/html, Size: 4306 bytes --]

  reply	other threads:[~2017-06-03 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 14:14 Thomas Petazzoni
2017-06-03 14:34 ` Khem Raj
2017-06-03 17:19   ` mzpqnxow [this message]
2017-06-03 20:14     ` Thomas Petazzoni
2017-06-03 20:13   ` Thomas Petazzoni
2017-06-03 22:50   ` mzpqnxow
2017-06-05  9:31     ` Thomas Petazzoni
2017-06-11  2:46       ` Rich Felker
2017-06-11 22:37         ` A. Wilcox

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=CA+qPFc+9dM9CtABhCFurO-X8L2GMKUu5-WEk0UkRxKQQkEZ5ZQ@mail.gmail.com \
    --to=musl@mzpqnxow.com \
    --cc=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).