Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Stephen Pape <srpape@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: VxWorks Target
Date: Wed, 19 Oct 2016 15:45:00 -0000	[thread overview]
Message-ID: <CAH=s-PP03ED32DoR5iEXP6ZL_8hNf-742Bj6jTF8pNdsy46SWA@mail.gmail.com> (raw)
In-Reply-To: <CADdUxCySVpsyBBNW2aabhP4h+VG9DGebpFD4u6VwK7UX6EK9NQ@mail.gmail.com>

On Wed, Oct 19, 2016 at 3:36 PM, Stephen Pape <srpape@gmail.com> wrote:
> Wow, so it's ancient history. If that's the case, there is some
> leftover VxWork code hanging around. I was even able to compile gdb
> with "--target=powerpc-vxworks", and there are a few files with the
> name still in the source:
>
> ./include/elf/vxworks.h
> ./bfd/elf-vxworks.c
> ./bfd/elf-vxworks.h
>
> The configure script has some VxWorks leftovers as well:
>
>   case "${target}" in
>     *-*-vxworks*)
>       # VxWorks uses the Dinkumware C++ library.
>       noconfigdirs="$noconfigdirs target-libstdc++-v3"
>       ;;
>

VxWorks support in GDB was removed, but its support in other
components, like linker, are still there.  They are not leftover.

However, configure should be adjusted so that gdb shouldn't
be configured at all if target is *-*-vxworks*.

-- 
Yao (齐尧)


  reply	other threads:[~2016-10-19 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 21:09 Stephen Pape
2016-10-19  8:17 ` Yao Qi
2016-10-19 14:36   ` Stephen Pape
2016-10-19 15:45     ` Yao Qi [this message]
2016-10-20 18:09       ` Stephen Pape
2016-10-20 18:47         ` Yao Qi
2016-10-21 15:30         ` Joel Brobecker
2016-10-26 15:51           ` Stephen Pape

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='CAH=s-PP03ED32DoR5iEXP6ZL_8hNf-742Bj6jTF8pNdsy46SWA@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=srpape@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