Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Feb 2007 14:28:54 +0200
From:      Andy Fawcett <andy@athame.co.uk>
To:        freebsd-ports@freebsd.org
Cc:        freebsd-stable@freebsd.org, "Jack L." <xxjack12xx@gmail.com>
Subject:   Re: Recent libxine update seems to cause ICE on 6-STABLE/amd64
Message-ID:  <200702181428.55734.andy@athame.co.uk>
In-Reply-To: <ab581e310702180104j38cd1ecbrf6fd425b727472d8@mail.gmail.com>
References:  <200702172132.18072.andy@athame.co.uk> <ab581e310702180104j38cd1ecbrf6fd425b727472d8@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 18 February 2007 11:04, Jack L. wrote:
> It fails to compile with the gcc version that comes with FreeBSD 6 and
> 7, but it compiles fine on gcc 4.1 when I tried. It's probably a
> compiler bug that's been fixed on the 4.x series.

Yes, I agree it builds fine on 6.2/amd64 when gcc 4.1 is used. I guess a 
simple fix for the port would be to update the USE_GCC version to a value 
known to work (4.1 and 4.2 from ports are ok, no idea about 4.0).

Hopefully someone more familiar with the compiler suites would be able to fix 
the system compilers.

Andy


> On 2/17/07, Andy Fawcett <andy@athame.co.uk> wrote:
> > On Thursday, libxine was updated in the ports collection to version 1.1.4
> >
> > Unfortunately, this seems to cause some kind of compiler-suite error on
> > 6.2-STABLE/amd64.
> >
> > dsputil.c:3826: error: unrecognizable insn:
> > (insn 62 10 12 0 (set (reg:SI 0 ax [61])
> >         (subreg:SI (plus:DI (subreg:DI (reg:SI 7 sp) 0)
> >                 (const_int -4 [0xfffffffffffffffc])) 0)) -1 (nil)
> >     (nil))
> > dsputil.c:3826: internal compiler error: in extract_insn, at recog.c:2083
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://gcc.gnu.org/bugs.html>; for instructions.
> > gmake[5]: *** [dsputil.lo] Error 1
> > gmake[5]: Leaving directory
> > `/usr/ports/multimedia/libxine/work/xine-lib-1.1.4/src/libffmpeg/libavcod
> >ec'
> >
> > Please see PR ports/109213 (raised by another person) for slightly more
> > context to the error. It's bitten two of us so far, apparently in
> > identical way.
> >
> > I'm not sure this should be a ports PR, maybe it should go to the
> > compiler suite?
> >
> > Andy
> >
> > --
> > Andy Fawcett                                     | andy@athame.co.uk
> >
> >                                                  | tap@kde.org
> >
> > "In an open world without walls and fences,      | tap@lspace.org
> >   we wouldn't need Windows and Gates."  -- anon  | tap@fruitsalad.org
> > _______________________________________________
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"

-- 
Andy Fawcett                                     | andy@athame.co.uk
                                                 | tap@kde.org
"In an open world without walls and fences,      | tap@lspace.org
  we wouldn't need Windows and Gates."  -- anon  | tap@fruitsalad.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200702181428.55734.andy>