gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-commit] [bug #38217] Testsuite build fails with undefined symbols


From: Sandro Santilli
Subject: [Gnash-commit] [bug #38217] Testsuite build fails with undefined symbols with --enable-visibility
Date: Tue, 09 Jul 2013 09:28:55 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0

Follow-up Comment #8, bug #38217 (project gnash):

People that want to save the most space output could as well add
--disable-testsuite. Those how don't will be able to run the testsuite, and
thus will need those symbols.

If you prefer testsuite to be enabled by default that's a different topic.

I'm against an --enable-visibility=testsuite because you'll be then be back to
"testsuite broken when adding --enable-visibility".

In any case the ./configure script should tell you if your configuration is
non-functional (ie: requested testsuite but can't run due to visibility).

To make things simple and chunkable, what about starting with the
TESTDSOEXPORT macro, currently defaulting to be an alias for DSOEXPORT ?  We
can discuss configure switches later

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?38217>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]