<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Let's start over again on my
SlackBuilds:<br>
<br>
/misc/gramps-3.3.1, games/ltris-1.018 & audio/puddletag-0.10.6<br>
all build fine on -current.<br>
<br>
system/krusader-2.3.0-beta1, desktop/wally-2.4.4 &
games/xye-0.12.0<br>
require changes to build on -current. See attached files.<br>
<br>
Thank you, Larry.<br>
<br>
Regards,<br>
Bill<br>
<br>
On 08/04/2012 11:20 PM, Larry Hajali wrote:<br>
</div>
<blockquote
cite="mid:CAAZPBMjxjgS7Y_0+ZsMsAWYMBihKOx=mWNLFqEjMocrVu03v5Q@mail.gmail.com"
type="cite">
<pre wrap="">xye, wally, and krusader do build with the appropriate patch or associated link.
xye 0.12.0 and 0.12.1 both build with the gcc-4.7.patch
wally 2.4.4 builds with the extra linker to X11 with
-DCMAKE_EXE_LINKER_FLAGS="-lX11" during the cmake step. The
disable-popup patch from previous versions should be included with
wally. Kind of annoying getting a popup box during compile time.
krusader 2.3.0-beta1 builds with the krusader-2.4.0_beta1-gcc47.patch
patch. Found from
<a class="moz-txt-link-freetext" href="http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/kde-misc/krusader/files/krusader-2.4.0_beta1-gcc47.patch?revision=1.1&view=markup&sortdir=down">http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/kde-misc/krusader/files/krusader-2.4.0_beta1-gcc47.patch?revision=1.1&view=markup&sortdir=down</a>
--Larry
On 8/4/12, B Kirkpatrick <a class="moz-txt-link-rfc2396E" href="mailto:bkirkp@gmail.com"><bkirkp@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Of my five SlackBuilds:
misc/gramps-3.3.1 & games/ltris-1.018
both build fine & seem to work OK. Only tested on x86-64.
system/krusader-2.4.0-beta1, desktop/wally-2.4.4 & games/xye-0.12.0
will not build.
There is a new release of gramps, 3.4.0, which builds & runs as well.
A new release of xye, 0.12.1 does not build.
Regards,
Bill Kirkpatrick
_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="http://slackbuilds.org/faq/">http://slackbuilds.org/faq/</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="http://slackbuilds.org/faq/">http://slackbuilds.org/faq/</a>
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>