My fix migrated (I forgot to reference this bug in the changelog)
** Changed in: mescc-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072472
Title:
** Changed in: mescc-tools (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072472
Title:
mescc-tools FTBFS on ppc64el
To manage notifications about this bug
** Bug watch added: Debian Bug tracker #1076187
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076187
** Also affects: mescc-tools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076187
Importance: Unknown
Status: Unknown
--
You received this bug notification
After remembering about gdb's starti command to start debugging at the
very first instruction, I think this is an upstream bug in the test and
filed https://github.com/oriansj/mescc-tools/issues/47 and will upload a
simple fix.
** Bug watch added: github.com/oriansj/mescc-tools/issues #47
same issue with 1.4 version of the package.
The elf stub provided in elf_headers/elf64-PPC64LE.hex2 does not point to the
entrypoint of hello.hex.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
mescc-tools fails to build on ppc64el with the following error:
test/test13/hello.sh
+ ./bin/M1 --little-endian --architecture ppc64le -f test/test13/hello.M1 -o
test/test13/hello.hex2
+ ./bin/hex2 --little-endian --architecture ppc64le --base-address 0x1
