Bug 85957 - make error in xine
make error in xine
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: gcc (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
: 85826 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-11 09:48 EST by mark harris
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-05 19:46:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mark harris 2003-03-11 09:48:29 EST
Description of problem:compile error


Version-Release number of selected component (if applicable):


How reproducible:when you compile the xine libs alpha 8 only happened since last
update to the latest kernel last one worked 
configure works but not make


Steps to Reproduce:
1.when you type make at the end you get the error
2.
3.
    
Actual results:


Expected results:


Additional info:
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
make[5]: *** [dsputil.lo] Error 1
make[5]: Leaving directory `/marks/xine-lib-1-beta8/src/libffmpeg/libavcodec'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/marks/xine-lib-1-beta8/src/libffmpeg/libavcodec'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/marks/xine-lib-1-beta8/src/libffmpeg'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/marks/xine-lib-1-beta8/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/marks/xine-lib-1-beta8'
make: *** [all] Error 2
Comment 1 Richard Henderson 2004-10-03 08:52:15 EDT
*** Bug 85826 has been marked as a duplicate of this bug. ***
Comment 2 Richard Henderson 2004-10-05 19:46:23 EDT
livna.org is building xine for Fedora, so I assume this works now.

Note You need to log in before you can comment on or make changes to this bug.