[Bug build/19302] New: Cannot cross-build a fully functional native djgpp gdb

["felix.von.s at posteo dot de" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19302

            Bug ID: 19302
           Summary: Cannot cross-build a fully functional native djgpp gdb
           Product: gdb
           Version: 7.10
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: felix.von.s at posteo dot de
  Target Milestone: ---
              Host: i686-pc-msdosdjgpp
            Target: i686-pc-msdosdjgpp
             Build: x86_64-unknown-linux-gnu

GDB cross-built as

./configure --{host,target}=i686-pc-msdosdjgpp --build=x86_64-unknown-linux-gnu

doesn't have native debugging enabled; you cannot load an .exe file and have it
run under GDB's supervision.

The reason is that config/mh-djgpp contains this:

  # Shorten the target alias so when it is used to set 'libsubdir'
  # the name will work in both short and long filename environments.
  ifeq ($(findstring -pc-msdosdjgpp,$(target_alias)),-pc-msdosdjgpp)
  target_alias=djgpp
  endif

The build scripts detect whether native debugging should be compiled in by
(character-wise) comparing target_alias to host_alias. However, the comparison
is performed AFTER the above shortening happens, and native debugging is
therefore kept disabled.

Since long file names are not a problem for me, I can just remove the offending
code, but clearly this isn't a complete solution.

It may seem a bit contrived, but I figure a similar bug may manifest when
someone sets, say, --host=i686-w64-mingw32 and --target=i486-pc-mingw32; the
triplets are effectively identical, but the build system won't notice this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.