the 'all' target. Better solution?
Thanks...
--
-Mike Melanson
code. We
felt it was better to roll with a version that compiled the current code
and move forward with making the Player work on current Linux systems.
--
-Mike Melanson
or version 6. That sounds a *LOT* easier than all the hacks you
mention in your blog.
At least 2 problems:
1) Having 2 binaries would immediately double the QA effort.
2) So far, there is only one version of gcc that can compile the Flash
Player and it is tied to libstdc++ v6.
--
-Mike Melanson
Mike Melanson wrote:
Hi,
Is it possible to configure the autotools to force a static link of a
particular libstdc++ library, ideally via an elegant solution in the
Makefile.am file?
Thanks for the assistance on this issue. We eventually produced a
satisfactory solution based partially on
app and the plugin?
Thanks...
--
-Mike Melanson
(it may be worse for both).
Generally, I'd consider it ugly.
Fortunately, all we are targetting with this binary is Linux/x86 systems.
--
-Mike Melanson
hout shared components). So we have a shared library plugin comprised
mostly of PIC code but with a few non-PIC components. It works unless
you have certain configuration options enabled, such as the secure
SELinux stuff.
--
-Mike Melanson
Ralf Wildenhues wrote:
Hello Mike,
* Mike Melanson wrote on Tue, Sep 19, 2006 at 07:22:12PM CEST:
Is it possible to configure the autotools to force a static link of a
particular libstdc++ library, ideally via an elegant solution in the
Makefile.am file?
I'm afraid you have to be
Hi,
Is it possible to configure the autotools to force a static link of a
particular libstdc++ library, ideally via an elegant solution in the
Makefile.am file?
Thanks...
--
-Mike Melanson
