Date
1 - 10 of 10
OpenColorIO FTBFS on GNU/kFreeBSD boxes
|
"Matteo F. Vescovi" <mfv.d...@...>
Hi!
The aim of a Debian Maintainer/Developer is to have a package building fine on all the supported archictures (actually, Debian supports 14 architectures officially, plus the unofficial ports). Now, Debian using kFreeBSD amd64/i386 kernel fails building, as you can see at [1] (Hurd is another story ;-) ). Any chance to get any help in solving this issue upstream? Thanks in advance. [1] https://buildd.debian.org/status/package.php?p=opencolorio -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A |
|
|
|
"Matteo F. Vescovi" <mfv.d...@...>
On Wed, Sep 11, 2013 at 05:07:37PM +0200, Matteo F. Vescovi wrote:
Now, Debian using kFreeBSD amd64/i386 kernel fails building, as you canUPDATE: a test build on a Debian GNU/kFreeBSD64 porterbox now gives the results attached in the buildlog file, where fail is probably related to the recent upgrade to boost 1.54 in Debian. Hope it could help fixing the issue. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A |
|
|
|
Jeremy Selan <jeremy...@...>
Thanks for this report.
toggle quoted message
Show quoted text
It looks to be a symbol visibility issue related to our use of yaml-cpp, so this is probably fixable by editing the top-level CMakeLists file's "USE_EXTERNAL_YAML" section. I dont have access to a box to test this unfortunately. Would anyone have access to a compile machine which demonstrates this issue? -- Jeremy On Thu, Sep 12, 2013 at 7:39 AM, Matteo F. Vescovi <mfv.d...@...> wrote:
On Wed, Sep 11, 2013 at 05:07:37PM +0200, Matteo F. Vescovi wrote:Now, Debian using kFreeBSD amd64/i386 kernel fails building, as you canUPDATE: a test build on a Debian GNU/kFreeBSD64 porterbox now gives the |
|
|
|
"Matteo F. Vescovi" <mfv.d...@...>
Hi!
On Mon, Sep 23, 2013 at 11:03:20AM -0700, Jeremy Selan wrote: Thanks for this report.Good to know ;-) I dont have access to a box to test this unfortunately. Would anyoneWell... I can test it, obviously ;-P Gonna let you know the results of the build with that parameter set. Thanks for your help. Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A |
|
|
|
Jeremy Selan <jeremy...@...>
Oh - on further inspection I see you're compiling against yaml 0.5.1
This is a known issue, being tracked here: https://github.com/imageworks/OpenColorIO/issues/318 -- Jeremy On Mon, Sep 23, 2013 at 12:40 PM, Matteo F. Vescovi <mfv.d...@...> wrote: Hi! |
|
|
|
Jeremy Selan <jeremy...@...>
We've just put out the 1.0.9 tag. Please see if this fixes things?
toggle quoted message
Show quoted text
On Mon, Sep 23, 2013 at 12:42 PM, Jeremy Selan <jeremy...@...> wrote:
Oh - on further inspection I see you're compiling against yaml 0.5.1 |
|
|
|
"Matteo F. Vescovi" <mfv.d...@...>
Hi again! Il giorno 23/set/2013 21:59, "Jeremy Selan" <jeremy...@...> ha scritto:
> > We've just put out the 1.0.9 tag. Please see if this fixes things? Perfect. Thanks a lot for the efforts. Cheers. -- |
|
|
|
"Matteo F. Vescovi" <mfv.d...@...>
Hi!
On Mon, Sep 23, 2013 at 10:03:32PM +0200, Matteo F. Vescovi wrote: Gonna check it tomorrow afternoon CET ;-)Just tested and added a link to buildlog in #318 issue. Hope it helps, somehow. Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A |
|
|
|
"Matteo F. Vescovi" <mfve...@...>
Hi!
On Tue, Sep 24, 2013 at 03:42:15PM +0200, Matteo F. Vescovi wrote: Hi!Any news on this front? OCIO is stuck to v1.0.8 in Debian because we already have yaml-cpp 0.5.x in sid/unstable suite and now OCIO is ftbfs against this new version. Could you possibly let me know what's the plan here? Thanks in advance. Cheers. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A |
|
|
|
Malcolm Humphreys <malcolmh...@...>
Hi Matteo can you checkout https://github.com/imageworks/OpenColorIO/pull/345 and see if this solves the issue for building against yaml-cpp-0.5.x? before we merge this into master. .malcolm On 12/12/2013, at 2:41 PM, Matteo F. Vescovi wrote:
|
|
|