All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu 0.5.3: qemu-fast
Date: Sun, 4 Apr 2004 14:51:07 -0400	[thread overview]
Message-ID: <20040404185107.GA30158@jbrown.mylinuxbox.org> (raw)

On Sat, Apr 03, 2004 at 05:39:33PM -0500, Jim C. Brown wrote:
> I tried to test the current CVS but I was unable to compiled using either
> gcc 3.0.4 or gcc 2.96 (the one by redhat) getting this error:
> 
> /usr/include/stdint.h:59: warning: redefinition of `uint64_t'
> /home/jbrown105/qemu/qemu/dyngen-exec.h:28: warning: `uint64_t' previously declared here
> /home/jbrown105/qemu/qemu/cpu-exec.c: In function `cpu_x86_exec':
> /home/jbrown105/qemu/qemu/cpu-exec.c:478: more than 10 operands in `asm'
> make[1]: *** [cpu-exec.o] Error 1
> make[1]: Leaving directory `/home/jbrown105/qemu/qemu.old/i386-user'
> make: *** [all] Error 1
> 

Upgrading to gcc 3.3.2, while a pain, fixed this.

I found a strange problem when compiling 0.5.3, however. The output is pasted
at the end of this email. It seems to be related to static vs shared linking.
When I alter the Makefile to remove the -static flag, the object files have
undefined references to __longjmp and such. I solved it by doing changing the
Makefile to do this:

/opt/gcc33/bin/gcc3  -static -Wl,-T,/home/jbrown105/qemu-0.5.3/i386-vl.ld  -o
qemu-fast vl.o osdep.o block.o monitor.o ide.o ne2000.o pckbd.o vga.o sb16.o
dma.o oss.o fdc.o mc146818rtc.o serial.o i8259.o i8254.o pc.o gdbstub.o sdl.o
libqemu.a -lm -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lm -L/usr/lib
-ldl -lutil -shared -lartsc -DPIC -fPIC -lpthread -L/usr/lib -lesd -laudiofile
-lm -L/usr/X11R6/lib -lX11 -lXext -lXxf86vm -lXxf86dga -lXv

So the libraries which cause trouble are linked shared but the object files
themselves and glibc itself are linked staticly. This seems to work, although
I haven't tried any real testing yet (just "qemu-fast --help"). I searched the
archives for information on this but I didn't find any, so I'm sending the info
here. (And yes I realize that I have this error because my system is broken.)

----OUTPUT ATTACHED----
# /opt/gcc33/bin/gcc3  -static -Wl,-T,/home/jbrown105/qemu-0.5.3/i386-vl.ld  -o qemu-fast vl.o osdep.o block.o monitor.o ide.o ne2000.o pckbd.o vga.o sb16.o dma.o oss.o fdc.o mc146818rtc.o serial.o i8259.o i8254.o pc.o gdbstub.o sdl.o libqemu.a -lm -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lm -L/usr/lib -ldl -lartsc -DPIC -fPIC -lpthread -L/usr/lib -lesd -laudiofile -lm -L/usr/X11R6/lib -lX11 -lXext -lXxf86vm -lXxf86dga -lXv -ldl -lutil
/usr/lib/libSDL.a(SDL_x11gl.lo)(.text+0x77b): In function `X11_GL_LoadLibrary':
: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/libesd.a(esdlib.o)(.text+0x4a2): In function `esd_connect_tcpip':
: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/X11R6/lib/libX11.a(x11trans.o)(.text+0x7a7): In function `_X11TransSocketINETConnect':
: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/libSDL.a(SDL_fbevents.lo)(.text+0x996): In function `find_pid':
: undefined reference to `__ctype_b'
/usr/lib/libSDL.a(SDL_fbelo.lo)(.text+0x480): In function `eloSendQuery':
: undefined reference to `__ctype_toupper'
/usr/lib/libSDL.a(SDL_fbelo.lo)(.text+0x602): In function `eloInitController':
: undefined reference to `__ctype_tolower'
/usr/lib/libartsc.a(ltdl.o)(.text+0x1074): In function `lt_dlopen':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(ConnDis.o)(.text+0x176): In function `_X11TransConnectDisplay':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(ConnDis.o)(.text+0x1fa): In function `_X11TransConnectDisplay':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(x11trans.o)(.text+0x66e): In function `_X11TransSocketINETConnect':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(x11trans.o)(.text+0xebe): In function `_X11TransSelectTransport':
: undefined reference to `__ctype_tolower'
/usr/X11R6/lib/libX11.a(x11trans.o)(.text+0xec4): In function `_X11TransSelectTransport':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(x11trans.o)(.text+0x1ac0): In function `is_numeric':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(XKBBind.o)(.text+0x106d): In function `XkbTranslateKeySym':
: undefined reference to `__ctype_toupper'
/usr/X11R6/lib/libX11.a(lcFile.o)(.text+0x1d): In function `parse_line':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(lcFile.o)(.text+0x219): In function `resolve_name':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(XlcDL.o)(.text+0x1d): In function `parse_line':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(XlcDL.o)(.text+0x45): In function `parse_line':
: undefined reference to `__ctype_b'
/usr/X11R6/lib/libX11.a(XlcDL.o)(.text+0x1b5): In function `resolve_object':
: undefined reference to `__ctype_b'
collect2: ld returned 1 exit status

                 reply	other threads:[~2004-04-04 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040404185107.GA30158@jbrown.mylinuxbox.org \
    --to=jbrown106@phreaker.net \
    --cc=jbrown106@swift-mail.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.