latest git fails to compile, amstream.c:77: undefined ref to `IID_IUnknown'

[Michael Ploujnikov]

git revision: ded4fbcc3c0d1e5f65cfb4e0e575f111c1e8974a

I get the following:

../../tools/winegcc/winegcc -B../../tools/winebuild -shared
./amstream.spec amstream.o main.o mediastream.o regsvr.o
version.res -Wl,--rpath,\$ORIGIN/`../../tools/relpath
/usr/local/lib/wine /usr/local/lib` -o amstream.dll.so -lole32 -luser32
-ladvapi32 -lkernel32 -lstrmiids -luuid ../../libs/port/libwine_port.a
-L/emul/linux/x86/usr/lib -L/emul/linux/x86/lib
amstream.o: In function `IAMMultiMediaStreamImpl_QueryInterface':
/home/plouj/apps/wine-git/dlls/amstream/amstream.c:77: undefined
reference to `IID_IUnknown'
main.o: In function `AMCF_QueryInterface':
/home/plouj/apps/wine-git/dlls/amstream/main.c:87: undefined reference
to `IID_IUnknown'
/home/plouj/apps/wine-git/dlls/amstream/main.c:87: undefined reference
to `IID_IClassFactory'
main.o: In function `DllGetClassObject':
/home/plouj/apps/wine-git/dlls/amstream/main.c:176: undefined reference
to `IID_IClassFactory'
/home/plouj/apps/wine-git/dlls/amstream/main.c:176: undefined reference
to `IID_IUnknown'
mediastream.o: In function `IMediaStreamImpl_QueryInterface':
/home/plouj/apps/wine-git/dlls/amstream/mediastream.c:74: undefined
reference to `IID_IUnknown'
collect2: ld returned 1 exit status
winegcc: gcc failed.
make[2]: *** [amstream.dll.so] Error 2
make[2]: Leaving directory `/home/plouj/apps/wine-git/dlls/amstream'
make[1]: *** [amstream] Error 2
make[1]: Leaving directory `/home/plouj/apps/wine-git/dlls'
make: *** [dlls] Error 2

I compile wine using the following script because I'm running on a
Gentoo 64bit machine:
$ cat build.sh
#!/bin/bash

./configure --x-libraries=/emul/linux/x86/usr/lib/ \
LDFLAGS="-L/emul/linux/x86/usr/lib -L/emul/linux/x86/lib" && \
make depend && \
make && \
./wine --version && \
echo "use find . -name '*.o' -exec rm \"{}\" \; to cleanup after the
compilation"

I've successfully compiled wine 0.9.14-0.9.17 from CVS with this
script.

Someone suggested that my LDFLAGS is could be messing up configure and
makes it use my system's libuuid instead of wines. I have found the
following libraries on my system:

$ locate libuuid
/mnt/gentoo32/lib/libuuid.so.1.2
/mnt/gentoo32/lib/libuuid.so
/mnt/gentoo32/lib/libuuid.so.1
/mnt/gentoo32/usr/lib/libuuid.a
/mnt/gentoo32/usr/lib/libuuid.so
/usr/lib64/libuuid.a
/usr/lib64/libuuid.so
/emul/linux/x86/lib/libuuid.so.1.2
/emul/linux/x86/lib/libuuid.so
/emul/linux/x86/lib/libuuid.so.1
/home/plouj/apps/wine-0.9.2/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.2/dlls/libuuid.a
/home/plouj/apps/wine-0.9.5/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.5/dlls/libuuid.a
/home/plouj/apps/wine-0.9.6/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.6/dlls/libuuid.a
/home/plouj/apps/wine-0.9.7/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.7/dlls/libuuid.a
/home/plouj/apps/wine-0.9.9/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.9/dlls/libuuid.a
/home/plouj/apps/wine-0.9.10/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.10/dlls/libuuid.a
/home/plouj/apps/wine-0.9.11/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.12/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.13/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.14/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.15/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.16/dlls/uuid/libuuid.a
/home/plouj/apps/wine-0.9.17/dlls/uuid/libuuid.a
/lib64/libuuid.so.1.2
/lib64/libuuid.so
/lib64/libuuid.so.1
/initrd/lib/libuuid.so.1
/initrd/lib/libuuid.so.1.2

Let me know if it would be appropriate to mail this to
wine-...@winehq.org

[Daniel Skorka]

Michael Ploujnikov <plo...@gmail.com> wrote:
> Let me know if it would be appropriate to mail this to
> wine-...@winehq.org

I am by no means an expert when it comes to 64bit systems, but here's my
two cents:
The code in the repository can break at any given time. Breaking
includes failure to compile. Maybe this only happens on 64bit platforms,
which is why nobody has noticed yet. My advice is to wait at least 4
days from time of breakage, check again and report to wine-devel if
still broken.

Daniel
>

[Paul Romanyszyn]

did you try make clean or make distclean after a ./configure
Compile errors can be the results of left overs when files or
directories are moved.
Also anytime you compile a new version and things don't seem correct do
a clean rebuild.
Paul R.

[Michael Ploujnikov]

> did you try make clean or make distclean after a ./configure
> Compile errors can be the results of left overs when files or
> directories are moved.

Yup, I got the error as soon as I checked out from git, and on
consecutive tries after doing 'make distclean'.

> Also anytime you compile a new version and things don't seem correct do
> a clean rebuild.

I assume you refer to the above.

[Michael Ploujnikov]

Well, I was able to successfully build git revision
6a97f2202e91fed286ff6ca254926e5f57ca17c1 so this topic is closed.

[Christoph Frick]

On Mon, Jul 17, 2006 at 03:39:31PM -0700, Michael Ploujnikov wrote:

> Well, I was able to successfully build git revision
> 6a97f2202e91fed286ff6ca254926e5f57ca17c1 so this topic is closed.

this is a problem, that seemed to exist for a few days on gcc32
compiles. Alexandre fixed this yesterday. please get the current
version.

--
cu