public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brandon Low <lostlogic@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GCC3.1 warnings
Date: Wed, 19 Jun 2002 21:18:09 -0500	[thread overview]
Message-ID: <20020619211809.A21203@lostlogicx.com> (raw)
In-Reply-To: <20020620015205.GE13457@athlon.dolly-llama.org>; from lamer@gentoo.org on Wed, Jun 19, 2002 at 08:52:05PM -0500

Information from the horses mouth as it were (as I'm the one currently 
working on the xine ebuilds):

1) Please report any problems with xine-0.9.10-r1 ebuilds to me, as AFAIK 
they should work on all compilers and all supported ARCHs (PPC and X86)

2) Thos flags are set in the xine makefiles, and I am considering 
using a compiler dependant patch to make it use the correct flags

3) xine-0.9.10 is no longer masked, however xine-d4d and xine-d5d do not 
work with it, so beware.  

Have fun watching movies, I personally have watched 3 movies in the past 
24 hours using xine, my dxr3 card, and the pcre on the fly mpeg encoding 
functions of xine... working great so far!

--Brandon

On Wed, 06/19/02 at 20:52:05 -0500, Ben Lutgens wrote:
> On Thu, Jun 20, 2002 at 10:29:06AM +0900, Jack Morgan wrote:
> >Did you get xine to compile. Xine-lib did but not xine-ui for me.
> 
> 
> 
> FWIW both compiled and worked great for me (I used the latest versions
> which I'm sure still are package masked)




  reply	other threads:[~2002-06-20  2:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20  0:38 [gentoo-dev] GCC3.1 warnings Justin Lambert
2002-06-20  1:29 ` Jack Morgan
2002-06-20  1:52   ` Ben Lutgens
2002-06-20  2:18     ` Brandon Low [this message]
2002-06-20  1:51 ` Ben Lutgens
2002-06-20  2:16   ` Jack Morgan
2002-06-20  2:21     ` Brandon Low

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=20020619211809.A21203@lostlogicx.com \
    --to=lostlogic@gentoo.org \
    --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