public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ian Phillips" <ianp@tibco.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Mozilla "patch" for flash/linux/GCC3.1
Date: Fri, 28 Jun 2002 11:43:40 +0100	[thread overview]
Message-ID: <3D1C3DDC.4000503@tibco.com> (raw)
In-Reply-To: 20020627170109.84990AC7EF@chiba.3jane.net

Hmmm, maybe the correct ebuild for this would be GCC3.1, then it's available to 
any other app that needs it.

This leaves us the problem of how to alter other apps to preload this patch. 
Could we make it a system wide environment setting? Would this break anything if 
all programs preloaded this lib?

That's a bad solution though. But the other option would be to patch every 
broken ebuild (admittedly, at present the only one I know of is Flash).

Here's my proposal then:

1. Patch GCC3.1 to build the shared library. This makes it available for any app
    that needs it. At the moment we only know about Flash, but it could in theory
    be anything that we install as a binary from a commercial vendor.
2. Patch Flash to check for a GCC3.1 based system. If found patch the mozilla
    start script to "export LD_PRELOAD=${LD_PRELOAD}:/usr/lib/libgcchack.so"
3. Patch any other app the same way if and when they are found.

Then we can remove individual patches from apps when the vendors make GCC3.1 
friendly releases.

Yours,
Ian.

-- 
#ifndef  __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | TIBCO Software Inc.
#endif                    | www.tibco.com





       reply	other threads:[~2002-06-28  8:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020627170109.84990AC7EF@chiba.3jane.net>
2002-06-28 10:43 ` Ian Phillips [this message]
     [not found] <20020628133202.12222AC7EF@chiba.3jane.net>
2002-06-28 15:35 ` [gentoo-dev] Re: Mozilla "patch" for flash/linux/GCC3.1 Ian Phillips
2002-06-28 16:50   ` Prashanth Aditya Susarla
     [not found] <20020627135803.42BF4AC79F@chiba.3jane.net>
2002-06-27 16:32 ` Ian Phillips
2002-06-27 16:03   ` Bart Verwilst
2002-06-27 16:34     ` José Fonseca

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D1C3DDC.4000503@tibco.com \
    --to=ianp@tibco.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox