Ok great! For the record, here is another slackware user with a similar
problem
http://www.linuxquestions.org/questions/slackware-14/trouble-building-musescore-on-slackware-64-a-4175454576/
lasconic
2013/7/31 David Woodfall <[email protected]>
> Hi lasconic,
>
> While watching a build that was teeing to a log I could pastebin, I
> noticed a linker error regarding libpthread, so I added -lpthread to
> CFLAGS and CXXFLAGS and it built fine.
>
> Thanks
>
> D.
>
> On (31/07/13 20:17), Lasconic <[email protected]> put forth the
> proposition:
> >Hi,
> >
> >We need more lines of the compilation log to help you. You can paste it on
> >http://paste.kde.org for example.
> >
> >lasconic
> >
> >
> >2013/7/31 David Woodfall <[email protected]>
> >
> >> I'm having problems building mscore:
> >>
> >> Linking CXX shared library libqtscript_gui.so
> >> make[3]: Leaving directory `/tmp/se/mscore-1.3/build'
> >> [ 95%] Built target qtscript_gui
> >> make[2]: Leaving directory `/tmp/se/mscore-1.3/build'
> >> make[1]: *** [all] Error 2
> >> make[1]: Leaving directory `/tmp/se/mscore-1.3/build'
> >> make: *** [release] Error 2
> >>
> >> I'm building on slackware 14.0 64bit
> >> qt 4.8.2
> >> cmake 2.8.8
> >>
> >> Any help would be great
> >>
> >> Thanks
> >>
> >>
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Get your SQL database under version control now!
> >> Version control is standard for application code, but databases havent
> >> caught up. So what steps can you take to put your SQL databases under
> >> version control? Why should you start doing it? Read more to find out.
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> >> _______________________________________________
> >> Mscore-developer mailing list
> >> [email protected]
> >> https://lists.sourceforge.net/lists/listinfo/mscore-developer
> >>
>
>
> >------------------------------------------------------------------------------
> >Get your SQL database under version control now!
> >Version control is standard for application code, but databases havent
> >caught up. So what steps can you take to put your SQL databases under
> >version control? Why should you start doing it? Read more to find out.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>
> >_______________________________________________
> >Mscore-developer mailing list
> >[email protected]
> >https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
>
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Mscore-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mscore-developer
>
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
