Bug 23854 (idct8x8_i386.c-error)

Summary: Build system doesn't work with -j2
Product: liboil Reporter: Michael Novick <mnovick1988>
Component: unknownAssignee: David Schleef <ds>
Status: NEW --- QA Contact: David Schleef <ds>
Severity: normal    
Priority: medium CC: mnovick1988
Version: HEAD   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: make log, (make -j2 CC=gcc-4.4 > make.log)

Description Michael Novick 2009-09-10 18:51:28 UTC
Created attachment 29400 [details]
make log, (make -j2 CC=gcc-4.4 > make.log)

while Compiling source from SVN(9-10-09) on Linux/i686(Ubuntu Karmic Koala-9.10-DEV)

The Compiling error happens...:
--------------
idct8x8_i386.c:390: error: â_oil_function_class_idct8x8_s16â undeclared here (not in a function)
--------------

This may be system related, im am unsure,(casual compiler, no programming experience)

System Specs:|
-------------|
GCC-4.4
Autoconf-2.64
Automake-1.11b
Pentuim4-I686
System type:1686
Comment 1 David Schleef 2009-09-10 19:01:27 UTC
Don't use -j2.  It doesn't work for liboil.

Let me know if this actually fixes the problem.
Comment 2 Michael Novick 2009-09-10 19:04:11 UTC
./configure --enable-dependency-tracking --enable-prototype-checking --enable-bren-implementations --enable-new-abi  --enable-gtk-doc --prefix=/usr CC=gcc-4.4

forgot to include...
Comment 3 Michael Novick 2009-09-10 19:12:08 UTC
no, not including jobs switch, just caused a ld error(which is strange), im going to clean and run again, to verify for compiling errors...

if it compiles, ill, close this report, otherwise, ill leave it open.
Comment 4 Michael Novick 2009-09-10 19:22:14 UTC
yes, jobs switch was causing my first compiling errors, now i recieve ld errors when including "--enable-new-abi".

it compiles fine without it though...
Comment 5 David Schleef 2010-02-04 11:44:46 UTC
Oops, forgot to reply to this.  Don't use --enable-new-abi, it's experimental, and apparently broken.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.