On Fri, Oct 03, 2014 at 05:24:55PM +0200, Matthias Klose wrote:
Am 02.10.2014 um 20:41 schrieb Aurelien Jarno:
On Tue, Sep 30, 2014 at 06:10:27PM +0200, Aurelien Jarno wrote:
On Fri, Sep 12, 2014 at 07:34:36PM +0200, Matthias Klose wrote:
Am 12.09.2014 um 15:13 schrieb Thibaut Paumard:
Am 02.10.2014 um 20:41 schrieb Aurelien Jarno:
On Tue, Sep 30, 2014 at 06:10:27PM +0200, Aurelien Jarno wrote:
On Fri, Sep 12, 2014 at 07:34:36PM +0200, Matthias Klose wrote:
Am 12.09.2014 um 15:13 schrieb Thibaut Paumard:
While it's your prerogative to decrease the severity, please note that
On Tue, Sep 30, 2014 at 06:10:27PM +0200, Aurelien Jarno wrote:
On Fri, Sep 12, 2014 at 07:34:36PM +0200, Matthias Klose wrote:
Am 12.09.2014 um 15:13 schrieb Thibaut Paumard:
While it's your prerogative to decrease the severity, please note that
this bug means that all the packages that
On Fri, Sep 12, 2014 at 07:34:36PM +0200, Matthias Klose wrote:
Am 12.09.2014 um 15:13 schrieb Thibaut Paumard:
While it's your prerogative to decrease the severity, please note that
this bug means that all the packages that build-depend on gdc (22
packages in jessie) are currently in an
Hi!
Iain Buclaw ibuc...@gdcproject.org writes:
If I can get to a port box with kfreebsd, I can investigate what is
going on further.
Axel (in CC) can probably set up an account on asdfasdf. I fear Steven's
vm has already expired which would have been a powerfull option as well
Christoph
--
On 27 September 2014 16:38, Christoph Egger christ...@debian.org wrote:
Hi!
Iain Buclaw ibuc...@gdcproject.org writes:
If I can get to a port box with kfreebsd, I can investigate what is
going on further.
Axel (in CC) can probably set up an account on asdfasdf. I fear Steven's
vm has
On 17:38, Christoph Egger wrote:
Axel (in CC) can probably set up an account on asdfasdf. I fear Steven's
vm has already expired which would have been a powerfull option as well
Yep, my VM is gone now. Hopefully the Debian porterbox will be up to
the task, but if not we can look into ways to
Hi,
On 13/09/14 19:01, Petr Salinger wrote:
Please try to grep undefined reference from your build log.
These errors do not lead to FTBFS, but they indicate some problem.
I've tried again building gcc-4.9 4.9.1-14 on a clean, sid
kfreebsd-amd64 system. I only removed gnu-kfreebsd from
On 14/09/14 19:30, Petr Salinger wrote:
No 'undefined reference' errors in the build log. Both regular and -m32
multilib versions of the static library are there:
I have problem with lgdruntime_t:
collect2: error: ld returned 1 exit status
Makefile:639: recipe for target 'unittest' failed
On 12/09/14 21:44, Petr Salinger wrote:
It seems that simple drop of kfreebsd-gnu from libphobos_no_systems does
not suffice.
In the build logs are messages like
/build/manual/gcc-4.9-4.9.1/build/x86_64-kfreebsd-gnu/libphobos/libdruntime/../../../../src/libphobos/libdruntime/rt/dmain2.d:419:
On 13 Sep 2014 18:51, Steven Chamberlain ste...@pyro.eu.org wrote:
On 12/09/14 21:44, Petr Salinger wrote:
It seems that simple drop of kfreebsd-gnu from libphobos_no_systems does
not suffice.
In the build logs are messages like
Package: gdc
Version: 4.9.1-4
Severity: grave
Hi,
gdc currently depends on libphobos-4.9-dev, including on kfreebsd-*, but
libphobos-4.9-dev is not beeing built on these architectures.
It may be that the bug is that libphobos should be built on kfreebsd.
From the gcc-4.9 build log:
Control: severity -1 important
Am 12.09.2014 um 12:47 schrieb Thibaut Paumard:
Package: gdc
Version: 4.9.1-4
Severity: grave
Hi,
gdc currently depends on libphobos-4.9-dev, including on kfreebsd-*, but
libphobos-4.9-dev is not beeing built on these architectures.
It may be that the
Processing control commands:
severity -1 important
Bug #761277 [gdc] gdc uninstallable on kfreebsd because of missing dep.
libphobos-4.9-dev
Severity set to 'important' from 'grave'
--
761277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761277
Debian Bug Tracking System
Contact
Le 12/09/2014 14:23, Matthias Klose a écrit :
Control: severity -1 important
Dear Matthias,
While it's your prerogative to decrease the severity, please note that
this bug means that all the packages that build-depend on gdc (22
packages in jessie) are currently in an FTBFS-state on kfreebsd.
Am 12.09.2014 um 15:13 schrieb Thibaut Paumard:
While it's your prerogative to decrease the severity, please note that
this bug means that all the packages that build-depend on gdc (22
packages in jessie) are currently in an FTBFS-state on kfreebsd.
sure, and they still will ftbfs without
Le 12/09/2014 19:34, Matthias Klose a écrit :
Am 12.09.2014 um 15:13 schrieb Thibaut Paumard:
While it's your prerogative to decrease the severity, please note that
this bug means that all the packages that build-depend on gdc (22
packages in jessie) are currently in an FTBFS-state on
Am 12.09.2014 um 15:13 schrieb Thibaut Paumard:
While it's your prerogative to decrease the severity, please note that
this bug means that all the packages that build-depend on gdc (22
packages in jessie) are currently in an FTBFS-state on kfreebsd.
sure, and they still will ftbfs without
18 matches
Mail list logo
