[mythtv] Issues with 0.26, gentoo, and zeromq
Marc Tousignant
myrdhn at gmail.com
Thu Oct 4 21:20:39 UTC 2012
-----Original Message-----
From: mythtv-dev-bounces at mythtv.org [mailto:mythtv-dev-bounces at mythtv.org]
On Behalf Of Gavin Hurlbut
Sent: Thursday, October 04, 2012 12:29 PM
To: Development of MythTV
Subject: Re: [mythtv] Issues with 0.26, gentoo, and zeromq
On Wed, Oct 3, 2012 at 6:34 PM, Marc Tousignant <myrdhn at gmail.com> wrote:
> From what I can tell, It both is, and is not that line.
>
>
>
> The solution I found is attached. Not sure if there was a simpler
> solution or not, but it works and the install succeeds.
That will not be committed to our repo. Sorry, that would break things for
other distros, and should be unnecessary. It sounds like something is wrong
with the ebuild configs you are using.
_______________________________________________
mythtv-dev mailing list
mythtv-dev at mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-dev
I'm not asking for it to be committed, just putting it out there that you
have an issue with the config files and this fixes it for my ebuild.
Zeromq didn't exist before 0.26, and I ran into install failures when
upgrading.
I have not made any changes to my ebuild between 0.25 and 0.26 and the
failures only occurred in the zeromq section, so that is where the issue is.
Something in the config section for that area is double stacking the
DESTDIR.
Removing the DESTDIR section of the line I commented on in my original post
ended up making some, but not all, of the files attempt to install directly
into / instead of to the image folder, thus causing a sandbox violation.
Someone actually reported these failures along with some others when he
attempted to create his own variation of my ebuild back in june to the users
list also trying to use master.
I'm going to investigate the issue and see if it works in the 0.26 pre
ebuild that was created in July. If it does, I will modify my ebuilds to
correct this issue. However, considering what I have discovered, I still
believe the issue lay in the config files in the myth sources, but I will
not say it's the only way to fix it, as it does break other distros.
MarcT
More information about the mythtv-dev
mailing list