gnash [ was Re: KDE4 ? ]

Ken Moffat zarniwhoop at
Mon Apr 20 17:04:06 PDT 2009

On Tue, Apr 21, 2009 at 01:35:57AM +0100, lux-integ wrote:
> On Monday 20 April 2009 11:49:17 pm Ken Moffat wrote:
> > On Mon, Apr 20, 2009 at 08:39:10PM +0100, lux-integ wrote:
> > > I am still struggling with gnash
> >
> >  Anything I can help with ? 
>  I installed all the gnash dependencies I believe.  Configure yields the 
> folowing:-
 Yes, I think you did.  Just a couple of minor points -
> #######
>         MING flags are -I/usr/local/include
>         MING libs are -L/usr/local/lib -lz -lm -lgif -lpng -lming
>         MING version code is 00040200
>         MAKESWF is /usr/local/bin/makeswf
>         MTASC is /usr/local
>         MTASC CLASSPATH is /usr/share/ocaml/mtasc/std
>         HAXE is /usr/local
>         HAXE CLASSPATH is /usr/share/haxe/
>         SWFMILL is /usr/local/bin/swfmill
>         SWFC is /usr/local/bin/swfc
 I suspect none of the above are necessary, but it's a while since I
read the descriptions of them (and since I only have a 50% success
rate with you-tube videos, perhaps some of them are useful).

>         XPCOM flags are: -I/opt/firefox-3.0.5/include/firefox-3.0.5/unstable
>         XPCOM libs 
> are: -L/opt/firefox-3.0.5/lib/firefox-devel-3.0.5/sdk/lib -lxpcomglue_s -lnspr4 -lplds4
 Unrelated to the gnash problem, but you need to keep abreast of
firefox updates.  And yes, I know I've kept quiet about 3.0.8 for
the -dev book, but at least the book does now point to where to
look for vulnerabilities, and also mentions about using the ff
tarball to build xulrunner.

 I'm also slightly surprised that you are able to build against
firefox rather than xulrunner - maybe you have better magic powers
than I do ;-)
> ###########
> when to type make,  it compiles for a while then fails with the following 
> message:-
> #######
> referenced in section 
> `.gnu.linkonce.r._ZN5boost11multi_index6detail13ordered_indexINS0_13composite_keyIN5gnash8PropertyENS0_6memberIS5_mXadL_ZNS5_5mNameEEEEENS6_IS5_mXadL_ZNS5_10mNamespaceEEEEENS_6tuples9null_typeESA_SA_SA_SA_SA_SA_SA_EESt4lessINS0_20composite_key_resultISB_EEENS1_9nth_layerILi1ES5_NS0_10indexed_byINS0_14ordered_uniqueISB_N4mpl_2naESK_EENSI_INS0_3tagINS4_12PropertyList5oTypeESK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_EENS6_IS5_iXadL_ZNS5_8mOrderIdEEEEESK_EESK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_EESaIS5_EEENS_3mpl7vector0ISK_EENS1_18ordered_unique_tagEE16delete_all_nodesEPNS1_18ordered_index_nodeINS10_INS1_15index_node_baseIS5_ST_EEEEEE' 
> of ../libcore/vm/.libs/libgnashvm.a(Machine.o): defined in discarded section 
> `.gnu.linkonce.t._ZN5boost11multi_index6detail13ordered_indexINS0_13composite_keyIN5gnash8PropertyENS0_6memberIS5_mXadL_ZNS5_5mNameEEEEENS6_IS5_mXadL_ZNS5_10mNamespaceEEEEENS_6tuples9null_typeESA_SA_SA_SA_SA_SA_SA_EESt4lessINS0_20composite_key_resultISB_EEENS1_9nth_layerILi1ES5_NS0_10indexed_byINS0_14ordered_uniqueISB_N4mpl_2naESK_EENSI_INS0_3tagINS4_12PropertyList5oTypeESK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_EENS6_IS5_iXadL_ZNS5_8mOrderIdEEEEESK_EESK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_SK_EESaIS5_EEENS_3mpl7vector0ISK_EENS1_18ordered_unique_tagEE16delete_all_nodesEPNS1_18ordered_index_nodeINS10_INS1_15index_node_baseIS5_ST_EEEEEE' 
> of
> ......
> `.gnu.linkonce.t._ZN5gnash12PropertyListD1Ev' 
> of ../libcore/vm/.libs/libgnashvm.a(Machine.o)
> collect2: ld returned 1 exit status
> make[3]: *** [] Error 1
> ######
> help will be much appreciated.
 I _think_ the error was just *before* "referenced in section".  All
I can see from what you posted is that something in Machine.o within
.libs/libgnashvm.a is defined in a "discarded section".

 Have you looked at what is in fedora (fc-11) ?  Or gentoo ?

 The error might be from binutils (clfs patches aggressively from
upstream), but if that was the case I would have expected similar
errors to show up a long time before you got to this part of your
build, so I think that is unlikely.

das eine Mal als Tragödie, das andere Mal als Farce

More information about the blfs-support mailing list