#877072 quantlib: build with -g to get debug information in the -dbgsym packages

#877072#5
Date:
2017-09-28 12:38:29 UTC
From:
To:
The -dbgsym packages are currently empty due to building with -g0.

Fix:
--- debian/rules.old	2017-09-27 15:50:24.943943210 +0000
+++ debian/rules	2017-09-27 15:51:43.240605464 +0000
@@ -42,7 +42,8 @@
 ## edd 18 Jul 2005	back to normal
 ## edd 17 Nov 2005	added -fpermissive for 0.3.11-2
 ## edd 13 Apr 2014      use buildflags as base
-compilerflags   = $(buildflags) -g0 -O2 -D_REENTRANT -fpermissive
+## bunk 28 Sep 2017     generate debug info, all buildds are now able to build with -g
+compilerflags   = $(buildflags) -g -O2 -D_REENTRANT -fpermissive

 # edd 14 Jan 2003  no longer override g++ as 3.2 is now default everywhere
 ## 			but use g++-3.0 on ia64


mips/mipsel with 2 GB userspace address space are our weakest
buildds, and I've verified that quantlib builds with this
change on mips.

#877072#10
Date:
2017-09-28 12:53:00 UTC
From:
To:
On 28 September 2017 at 15:38, Adrian Bunk wrote:
| Source: quantlib
| Version: 1.10.1-2
| Severity: normal
| Tags: patch
|
| The -dbgsym packages are currently empty due to building with -g0.

Won't fix.  A certain Adrian Bunk just made me override compilerflags, you
may want to talk to him ;-)

In all seriousness, I have maintained this for 15 years and just about each
and every time had to fight with 'too small' a build machine or architecture
to complete a build, either here or (equally) for quantlib-swig which sticks
all interfaces into one compilation unit.

The -g0 is here for a reason, and unless you demonstrate buildability on all
twelve (?) platforms I do not think I want to mess with this. Life's too short.

Dirk

|
| Fix:
|
| --- debian/rules.old	2017-09-27 15:50:24.943943210 +0000
| +++ debian/rules	2017-09-27 15:51:43.240605464 +0000
| @@ -42,7 +42,8 @@
|  ## edd 18 Jul 2005	back to normal
|  ## edd 17 Nov 2005	added -fpermissive for 0.3.11-2
|  ## edd 13 Apr 2014      use buildflags as base
| -compilerflags   = $(buildflags) -g0 -O2 -D_REENTRANT -fpermissive
| +## bunk 28 Sep 2017     generate debug info, all buildds are now able to build with -g
| +compilerflags   = $(buildflags) -g -O2 -D_REENTRANT -fpermissive
|
|  # edd 14 Jan 2003  no longer override g++ as 3.2 is now default everywhere
|  ## 			but use g++-3.0 on ia64
|
|
| mips/mipsel with 2 GB userspace address space are our weakest
| buildds, and I've verified that quantlib builds with this
| change on mips.

#877072#15
Date:
2017-09-28 12:53:00 UTC
From:
To:
On 28 September 2017 at 15:38, Adrian Bunk wrote:
| Source: quantlib
| Version: 1.10.1-2
| Severity: normal
| Tags: patch
|
| The -dbgsym packages are currently empty due to building with -g0.

Won't fix.  A certain Adrian Bunk just made me override compilerflags, you
may want to talk to him ;-)

In all seriousness, I have maintained this for 15 years and just about each
and every time had to fight with 'too small' a build machine or architecture
to complete a build, either here or (equally) for quantlib-swig which sticks
all interfaces into one compilation unit.

The -g0 is here for a reason, and unless you demonstrate buildability on all
twelve (?) platforms I do not think I want to mess with this. Life's too short.

Dirk

|
| Fix:
|
| --- debian/rules.old	2017-09-27 15:50:24.943943210 +0000
| +++ debian/rules	2017-09-27 15:51:43.240605464 +0000
| @@ -42,7 +42,8 @@
|  ## edd 18 Jul 2005	back to normal
|  ## edd 17 Nov 2005	added -fpermissive for 0.3.11-2
|  ## edd 13 Apr 2014      use buildflags as base
| -compilerflags   = $(buildflags) -g0 -O2 -D_REENTRANT -fpermissive
| +## bunk 28 Sep 2017     generate debug info, all buildds are now able to build with -g
| +compilerflags   = $(buildflags) -g -O2 -D_REENTRANT -fpermissive
|
|  # edd 14 Jan 2003  no longer override g++ as 3.2 is now default everywhere
|  ## 			but use g++-3.0 on ia64
|
|
| mips/mipsel with 2 GB userspace address space are our weakest
| buildds, and I've verified that quantlib builds with this
| change on mips.

#877072#20
Date:
2017-09-28 13:06:16 UTC
From:
To:
The reason was the hardware used to build Debian > 10 years ago.

We have 10 release architectures, and since it didn't blow up on
one with the lowest virtual address space I am quite confident
that it will build on the current buildds for any architecture.

cu
Adrian