Sync ldc 1:1.1.0-2 (universe) from Debian unstable (main)

Bug #1607432 reported by Matthias Klumpp
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ldc (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Please sync ldc 1:1.1.0-2 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * use-std-versions-cmath-ctype-functions.patch: Fix FTBFS
    with GCC 5.3. (LP: #1570006)

The FTBFS has been resolved upstream, that patch is no longer necessary and the packaging can be resynchronized with Debian.

Changelog entries since current yakkety version 1:0.17.1-1ubuntu1:

ldc (1:1.1.0-2) unstable; urgency=medium

  * Multiarch enable
  * Install includes separately to avoid clash with gdc (Closes: #827211)

 -- Konstantinos Margaritis <email address hidden> Thu, 14 Jul 2016 21:56:46 +0300

ldc (1:1.1.0-1) unstable; urgency=medium

  * New upstream release
  * Removed debug packages, dbgsym packages are provided.

 -- Konstantinos Margaritis <email address hidden> Sat, 09 Jul 2016 20:55:49 +0300

Matthias Klumpp (ximion)
Changed in ldc (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Jeremy Bícha (jbicha) wrote :

According to Debian's build logs, the package FTBFS on powerpc but the current ldc builds on Ubuntu's powerpc so that seems like it would be a regression.

https://buildd.debian.org/status/package.php?p=ldc
https://buildd.debian.org/status/logs.php?pkg=ldc&arch=powerpc

Revision history for this message
Matthias Klumpp (ximion) wrote :

Yeah, unfortunately we (LDC Debian maintainer and I) and upstream don't know yet why this fails (yet).
See https://github.com/ldc-developers/ldc/issues/1636
That segfault is weird...
It's likely that we will just drop the architecture from being built until this is fixed.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Could you talk to someone from ~ubuntu-archive about dropping the powerpc binaries then?

I don't want to sync this package if it will just get stuck in -proposed. Thanks!

Revision history for this message
Matthias Klumpp (ximion) wrote :

Will do - meanwhile, there is also another issue for Yakkety which needs to be addressed somehow - apparently LDC chokes on the Yakkety toolchain compiling everything with -fPIE by default now.
See https://github.com/ldc-developers/ldc/issues/1618#issuecomment-236229097 for details on that.

Revision history for this message
Matthias Klumpp (ximion) wrote :

I made a (working) patch for the PIE issue (attached), so the only remaining problem is the compilation issue on powerpc.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Even with your patch applied, I'm seeing the following build failure on yakkety/amd64:

[ 0%] Generating ddmd/idgen
cd /build/ldc-1.1.0 && /usr/bin/ldmd2 -wi -O -inline -release -J/build/ldc-1.1.0/ddmd -I/build/ldc-1.1.0/ddmd -of/build/ldc-1.1.0/build-static/ddmd/idgen ddmd/idgen.d
/usr/bin/ld: /build/ldc-1.1.0/build-static/ddmd/idgen.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
/build/ldc-1.1.0/build-static/ddmd/idgen.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Error: /usr/bin/gcc failed with status: 1
CMakeFiles/LDCShared.dir/build.make:68: recipe for target 'ddmd/idgen' failed

Changed in ldc (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Bícha (jbicha) wrote :

The sync has been done but it won't migrate until the powerpc binaries are removed:

https://launchpad.net/ubuntu/+source/ldc/1:1.1.0-2ubuntu2

Changed in ldc (Ubuntu):
status: Incomplete → Fix Committed
Revision history for this message
Matthias Klumpp (ximion) wrote :

Thank you!
I am poking the Debian maintainer to update the package, because the current one is actually an older Git snapshot of LDC, which has a few annoying bugs (like broken debug support...)
Cheers,
    Matthias

Matthias Klumpp (ximion)
Changed in ldc (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.