Re: [Qemu-devel] AMD64+Solaris10 compile

2006-10-13 Thread Martin Bochnig
Ishwar Rattan wrote:


 Is there a way to compile qemu-cvs-snapshot under Solaris-10 running
 on amd64 processor?

 -ishwar 



Take that:

http://www.martux.org/qemu/XXX__qemu-0.8.2-solaris__20061010x11_g.tar.gz
or
http://www.opensolaris.org/os/project/qemu/downloads/qemu-0.8.2-solaris.tar.gz
(will be sync'ed later today)

http://opensolaris.org/os/project/qemu/downloads/

M.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] AMD64+Solaris10 compile

2006-10-13 Thread Martin Bochnig
Eric Lowe wrote:

Is there a way to compile qemu-cvs-snapshot  under Solaris-10 running
on amd64 processor?



Check out the sources and instructions at 
http://www.opensolaris.org/os/project/qemu

There are some patches for 64-bit builds that I think still need to be 
committed to the main CVS source, you can create your own diffs -vs- the 0.8.2 
stock source to see what was done to get 64-bit builds to work and apply the 
same changes to the CVS source if you really want the latest. You may also 
need to update your gcc (such as with Blastwave gcc) if /usr/sfw/bin/gcc 
doesn't work. There you will also find a kqemu accelerator module which should 
work for Solaris 10.

- Eric




Ah, ok, Eric already did respond.

Nothing to add.


-MB


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] qemu and kernel 2.6.18

2006-10-13 Thread G Portokalidis

Hello all,
I have recently installed the latest linux kernel, and i have been
having problems with the tap interface since.

I have been getting the following cryptic message:
warning: could not configure /dev/net/tun: no virtual network emulation
Could not initialize device 'tap'

The tun driver is loaded, and /dev/net/tun is 'rw'.
Any ideas what this is about? Could i have misconfigured something in
the kernel?

Cheers,
George


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] qemu and kernel 2.6.18

2006-10-13 Thread WaxDragon

This came up in IRC a few days ago, it seems you need to use the UML
util 'tunctl' to assign permissions to the tap device.  I found this
change annoying.

On 10/13/06, G Portokalidis [EMAIL PROTECTED] wrote:

Hello all,
I have recently installed the latest linux kernel, and i have been
having problems with the tap interface since.

I have been getting the following cryptic message:
warning: could not configure /dev/net/tun: no virtual network emulation
Could not initialize device 'tap'

The tun driver is loaded, and /dev/net/tun is 'rw'.
Any ideas what this is about? Could i have misconfigured something in
the kernel?

Cheers,
George


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel




--
22:38 @WaxDragon false ^ true
22:39  false :(
22:39  false dont you think you can XOR me and get away with it! I
always return!


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Ishwar Rattan


Trying to compile qemu on amd64 based Solaris.

I do not have write permission to /usr/local subtree

./configure --libdir=other-path --prefix=not-ustlocal
is fine
but make always generates binaries that want to find
/usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).

What is the way out for this sticky point?

-ishwar



___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ishwar Rattan wrote:


 Trying to compile qemu on amd64 based Solaris.

 I do not have write permission to /usr/local subtree

 ./configure --libdir=other-path --prefix=not-ustlocal
 is fine
 but make always generates binaries that want to find
 /usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).


Where is the problem 64bit versus 32bit ?
(32 bit version of libSDL-1.2.so.0 found while amd64 64bit version needed?)
(should go under /usr/local/lib/amd64/libSDL-1.2.so.0)


 What is the way out for this sticky point?

 -ishwar




Read ld.so.1(1)
i.e.
# man ld.so.1

Then: One option is to set $LD_LIBRARY_PATH (or potentially
$LD_LIBRARY_PATH_64 [not required]).

bash:

# export LD_LIBRARY_PATH=/export/home/me/foo/mypersonallibs:$LD_LIBRARY_PATH

Did you set ./configure --prefix=SomeWritableLocation ?




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Ishwar Rattan



On Fri, 13 Oct 2006, Martin Bochnig wrote:


Ishwar Rattan wrote:




Where is the problem 64bit versus 32bit ?
(32 bit version of libSDL-1.2.so.0 found while amd64 64bit version needed?)
(should go under /usr/local/lib/amd64/libSDL-1.2.so.0)

Well, the problem is I do not root privileges so can't place libSL in
/usr/local/lib or /usr/local/lib/amd64.

I would like to  keep it in $HOME/lib and want qemu to see the lib 
archive.


I will try LD_LIBRARY_PATH option. Is to possible to have a staticly
linked version of libSDL in the qemu binaries?

-ishwar


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ishwar Rattan wrote:



 On Fri, 13 Oct 2006, Martin Bochnig wrote:

 Ishwar Rattan wrote:


 Where is the problem 64bit versus 32bit ?
 (32 bit version of libSDL-1.2.so.0 found while amd64 64bit version
 needed?)
 (should go under /usr/local/lib/amd64/libSDL-1.2.so.0)

 Well, the problem is I do not root privileges so can't place libSL in
 /usr/local/lib or /usr/local/lib/amd64.

 I would like to keep it in $HOME/lib and want qemu to see the lib
 archive.

 I will try LD_LIBRARY_PATH option. Is to possible to have a staticly
 linked version of libSDL in the qemu binaries?


The short answer is NO, not on SunOS = 5.10 .
Especially not for 64bit.
In particular not for 64bit_amd64.

You will hardly be able to meet the required dependencies.

I'm leaving over the weekend now, much luck with it.


 -ishwar





___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Ben Taylor

 Ishwar Rattan [EMAIL PROTECTED] wrote: 
 
 Trying to compile qemu on amd64 based Solaris.
 
 I do not have write permission to /usr/local subtree
 
 ./configure --libdir=other-path --prefix=not-ustlocal
 is fine
 but make always generates binaries that want to find
 /usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).
 
 What is the way out for this sticky point?

Manually add -L/usr/local/lib -R/usr/local/lib to the Makefile for the link
phase so it will correctly add those paths to the library lookup.  If I had
a code base to look at this instance, I could tell you where.  You could
also add those flags to Makefile.target in the SOLARIS specific areas,
which would probably make more sense.

As Martin indicated, setting LD_LIBRARY_PATH may get you a running
binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Ben Taylor

 Ishwar Rattan [EMAIL PROTECTED] wrote: 
 
 Trying to compile qemu on amd64 based Solaris.
 
 I do not have write permission to /usr/local subtree
 
 ./configure --libdir=other-path --prefix=not-ustlocal
 is fine
 but make always generates binaries that want to find
 /usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).
 
 What is the way out for this sticky point?

Manually add -L/usr/local/lib -R/usr/local/lib to the Makefile for the link
phase so it will correctly add those paths to the library lookup.  If I had
a code base to look at this instance, I could tell you where.  You could
also add those flags to Makefile.target in the SOLARIS specific areas,
which would probably make more sense.

As Martin indicated, setting LD_LIBRARY_PATH may get you a running
binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ben Taylor wrote:

 Ishwar Rattan [EMAIL PROTECTED] wrote: 
  

Trying to compile qemu on amd64 based Solaris.

I do not have write permission to /usr/local subtree

./configure --libdir=other-path --prefix=not-ustlocal
is fine
but make always generates binaries that want to find
/usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).

What is the way out for this sticky point?



Manually add -L/usr/local/lib -R/usr/local/lib 


Rather -L/his/home/sdl_amd64/lib -R/his/home/sdl_amd64/lib
Because I doubt, an amd64 version of libSDL is currently present in
/usr/local/lib/amd64
(and he doesn't have w access).

This method is btw not really new to me, see my posting from a few
hours ago:
http://www.opensolaris.org/jive/thread.jspa?threadID=15448tstart=0


to the Makefile for the link
phase so it will correctly add those paths to the library lookup.  If I had
a code base to look at this instance, I could tell you where.  You could
also add those flags to Makefile.target in the SOLARIS specific areas,
which would probably make more sense.

As Martin indicated, setting LD_LIBRARY_PATH may get you a running
binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.

Ben
  


 LD_LIBRARY_PATH is the wrong answer for Solaris
???
---  Weak statement.

It has its [dis]advantages.
Namely that the paths to a library are _not_ hardwired.
That's the exactly reason, why I did recommend it in this very scenario.
And I would do it again for Ishwar's current needs.

-M.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ishwar Rattan wrote:


 Also, I downloaded the SDL-1.2.11 source from opensolaris.org download
 page. I can't figure out how to apply the 64bit patch (patch rejects
 the diffs, a visual inspection shows that patch is already applied to the
 source?)

 -ishwar



Manually applying a patch will always work (vi or emacs -nw)

Regards
(leaving soon, really now)


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ben Taylor wrote:

As Martin indicated, setting LD_LIBRARY_PATH may get you a running
binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.

  


My answer had been a bit longer:

Read ld.so.1(1)
i.e.
# man ld.so.1

Then: *One* option is to set $LD_LIBRARY_PATH (or potentially
$LD_LIBRARY_PATH_64 [not required]).




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] qemu-system-sparc question?

2006-10-13 Thread Paul Brook
On Wednesday 11 October 2006 18:20, Blue Swirl wrote:
 Sounds like you just want a bare-metal cross. There's absolutely no reason
 to
 run the editor, compiler or assembler on the target machine.
 Many targets even have gdb simulators (MIPS, ARM and PPC do).

 I disagree, it's much easier to use a native compiler than to build a cross
 compiler, even with crosstool. 

Well, with native toolchains you get prebuilt binaries from your system 
vendor, so building them is a non-issue.

I don't believe that they're much easier to use in this context. If you're 
building prepackaged worktation software you might hit problems with crappy 
configure scripts. For a teaching environment I wouldn't expect it to be a 
problem, especially given the alternative is probably running on embedded dev 
boards.

 I don't think other compilers than GCC even support 
 cross setups.

That's definitely not true. Certainly anything targeting embedded systems are 
cross compilers (the target too small/slow to consider compiling natively), 
and I'd guess the same is true for many HPC systems (You don't want the 
clutter on your compute machines, esp. if they're used via batch jobs).
In my experience pretty much all development is done with cross compilers from 
workstations or commodity compile farms. This means windows/x86-linux, or 
maybe a few crufty old solaris boxes left over from when sparc was fast :-)

 BTW, we could easily design and implement an ideal CPU just for Qemu
 purposes. It could be unlike any existing hardware, for example with zero
 or thousands of registers. The problem would be making a compiler for the
 CPU, also porting some OS to it. Any GCC and Linux guru volunteers? CS
 research projects?

There's no such think as an Ideal cpu. It's like picking the right 
religion :-) If you want a toy cpu, there are things like mmix.
While arm, ppc, mips, sparc, etc each have their own peculiarities, they're 
all reasonably clean architectures. 

Paul


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Ben Taylor

 Martin Bochnig [EMAIL PROTECTED] wrote: 
 Ben Taylor wrote:
 
 As Martin indicated, setting LD_LIBRARY_PATH may get you a running
 binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.
 
   
 
 
 My answer had been a bit longer:
 
 Read ld.so.1(1)
 i.e.
 # man ld.so.1
 
 Then: *One* option is to set $LD_LIBRARY_PATH (or potentially
 $LD_LIBRARY_PATH_64 [not required]).

I'm not saying it doesn't work.  But properly compiled programs for
Solaris include the run time paths to the libraries so an LD_LIBRARY_PATH
environment variable is not required.

LD_LIBRARY_PATH is interesting to test out new versions of support
libraries without actually having to recompile, so it has it's uses.
but too often, folks use LD_LIBRARY_PATH as a panacea on Solaris
to fix poorly compiled programs.

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ben Taylor wrote:

 Martin Bochnig [EMAIL PROTECTED] wrote: 
  

Ben Taylor wrote:



As Martin indicated, setting LD_LIBRARY_PATH may get you a running
binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.

 

  

My answer had been a bit longer:

Read ld.so.1(1)
i.e.
# man ld.so.1

Then: *One* option is to set $LD_LIBRARY_PATH (or potentially
$LD_LIBRARY_PATH_64 [not required]).



I'm not saying it doesn't work.  But properly compiled programs for
Solaris include the run time paths to the libraries so an LD_LIBRARY_PATH
environment variable is not required.

LD_LIBRARY_PATH is interesting to test out new versions of support
libraries without actually having to recompile, so it has it's uses.
but too often, folks use LD_LIBRARY_PATH as a panacea on Solaris
to fix poorly compiled programs.

Ben
  



He is experimenting and trying out a bit.
Not building to be published packages.

I advised him to read and understand ld.so.1(1).
And I mentioned $LD_LIBRARY_PATH as *one* possible option for him to get
quick results.


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Ben Taylor

 Martin Bochnig [EMAIL PROTECTED] wrote: 
 Ben Taylor wrote:
 
  Ishwar Rattan [EMAIL PROTECTED] wrote: 
   
 
 Trying to compile qemu on amd64 based Solaris.
 
 I do not have write permission to /usr/local subtree
 
 ./configure --libdir=other-path --prefix=not-ustlocal
 is fine
 but make always generates binaries that want to find
 /usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).
 
 What is the way out for this sticky point?
 
 
 
 Manually add -L/usr/local/lib -R/usr/local/lib 
 
 
 Rather -L/his/home/sdl_amd64/lib -R/his/home/sdl_amd64/lib

Yeah, that.  brain fart when I was typing that.

 Because I doubt, an amd64 version of libSDL is currently present in
 /usr/local/lib/amd64
 (and he doesn't have w access).

Right. I knew what I meant, I just didn't type it right.

 This method is btw not really new to me, see my posting from a few
 hours ago:
 http://www.opensolaris.org/jive/thread.jspa?threadID=15448tstart=0
 
 
 to the Makefile for the link
 phase so it will correctly add those paths to the library lookup.  If I had
 a code base to look at this instance, I could tell you where.  You could
 also add those flags to Makefile.target in the SOLARIS specific areas,
 which would probably make more sense.
 
 As Martin indicated, setting LD_LIBRARY_PATH may get you a running
 binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.
 
 Ben
   
 
 
  LD_LIBRARY_PATH is the wrong answer for Solaris
 ???
 ---  Weak statement.

LD_LIBRARY_PATH is the wrong answer for Solaris.  It's great for
trying to fix problems like this when the app won't run with a particular
set of libraries, or you're testing with new libraries and you don't
want to recompile  (I've done this before).  Too many people use
it as a panacea for poorly compiled/configured Open source software.
In this case, he might just set the LD_LIBRARY_PATH and never
recompile it, even though it won't work if it uses the default LIB path.
 
 It has its [dis]advantages.
 Namely that the paths to a library are _not_ hardwired.

But then that requires a dependency on knowing where your
libraries are, and could possibly create an imcombaility by
overriding a library path for some other application that is
also leaning on LD_LIBRARY_PATH.  Obviously you can
get around this by encapsulating each application requiring
LD_LIBRARY_PATH, thereby negating the need for a user
or system wide LD_LIBRARY_PATH variable.

 That's the exactly reason, why I did recommend it in this very scenario.

In this case, I can agree for the purposes of a test.  But it also indicates
that some work is required for the Solaris port if other library paths
need to be linked in during the compliation/link phase.

 And I would do it again for Ishwar's current needs.

Works for me.

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Ben Taylor

 Ishwar Rattan [EMAIL PROTECTED] wrote: 
 
 
 On Fri, 13 Oct 2006, Martin Bochnig wrote:
 
  Ishwar Rattan wrote:
 
 
  Where is the problem 64bit versus 32bit ?
  (32 bit version of libSDL-1.2.so.0 found while amd64 64bit version needed?)
  (should go under /usr/local/lib/amd64/libSDL-1.2.so.0)
 Well, the problem is I do not root privileges so can't place libSL in
 /usr/local/lib or /usr/local/lib/amd64.
 
 I would like to  keep it in $HOME/lib and want qemu to see the lib 
 archive.
 
 I will try LD_LIBRARY_PATH option. 

It should work.  the main thing is to not to agressive with LD_LIBRARY_PATH in
this case.  Since it sounds like it already may be linking against 
/usr/local/lib
where the current libSDL is, you should just be able to add the new lib dir
to the LD_LIBRARY_PATH env variable, and then run ldd on qemu to make
sure it's finding the right libraries. When you have the right LD_LIBRARY_PATH,
then it should be working for you.

 Is to possible to have a staticly
 linked version of libSDL in the qemu binaries?

There is an option for statically linked libSDL in the qemu binaries, 
and I tried to make sure I kept that intact for solaris in the configure
script.  Try it and see what happens.  

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


[Qemu-devel] Re: Hello

2006-10-13 Thread Martin Bochnig
Ishwar Rattan wrote:



 I think the SDL source I downloaded is already prepatched.
 See the diff file below: my assumption is that --- indicates the
 original file and +++ the patched version (I might be wrong
 here). So, line in file with - in first column is reference to
 original file and is to be replaced by with line with + in
 first column.


Hi,

please ask Eric Lowe.
I did not prepare the x64/x86 stuff.
And the sdl amd64 bit patch is also from him.
The diff is not very big, that's true.
But it is not zero, I don't know.
I didn't build sdl for x64 so far.

I'm mostly the sparc guy.
I had been busy all week long in improving the src to better support
sparc-hosts.
Therefore didn't I come to amd64 so far, while I do intend to asap.

See my diff from yesterday (which is meanwhile totally obsolete again) :

http://www.martux.org/qemu/qemu-0.8.2-solaris__20061010x11.gdiff

Pls. gimme time until I throw the sparc pkg out before I can deeper look
into amd64-HOST support.


Thanks,
Martin


 diff -ur SDL-1.2.11.orig/configure SDL-1.2.11.jnz/configure
 --- SDL-1.2.11.orig/configure Tue Jun 27 06:48:54 2006
 +++ SDL-1.2.11.jnz/configure Mon Sep 4 15:28:28 2006
 @@ -33170,10 +33170,10 @@

 if test x$enable_rpath = xyes; then
 if test $ARCH = bsdi -o $ARCH = freebsd -o $ARCH = irix -o $ARCH =
 linux -o $ARCH = netbsd; then
 - SDL_RLD_FLAGS=-Wl,-rpath,\${exec_prefix}/lib
 + SDL_RLD_FLAGS=-Wl,-rpath,\${libdir}
 fi
 ...
 -- In configure file (of source distribution):
 Lines around 33170+ already have the replacement done?

 # Set runtime shared library paths as needed

 if test x$enable_rpath = xyes; then
 if test $ARCH = bsdi -o $ARCH = freebsd -o $ARCH = irix -o $ARCH =
 linux -o $ARCH = netbsd; then
 SDL_RLD_FLAGS=-Wl,-rpath,\${libdir}
 fi
 if test $ARCH = solaris; then
 ...

 I am stumped by why the compiled binaries do not work. This is the
 limit of my expertise. Can I find pre-patched SDL-1.2.11 source
 somewhere?


 Regards,
 -ishwar





___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ben Taylor wrote:

 Ishwar Rattan [EMAIL PROTECTED] wrote: 
  

On Fri, 13 Oct 2006, Martin Bochnig wrote:



Ishwar Rattan wrote:

  

Where is the problem 64bit versus 32bit ?
(32 bit version of libSDL-1.2.so.0 found while amd64 64bit version needed?)
(should go under /usr/local/lib/amd64/libSDL-1.2.so.0)
  

Well, the problem is I do not root privileges so can't place libSL in
/usr/local/lib or /usr/local/lib/amd64.

I would like to  keep it in $HOME/lib and want qemu to see the lib 
archive.

I will try LD_LIBRARY_PATH option. 



It should work.  the main thing is to not to agressive with LD_LIBRARY_PATH in
this case.  Since it sounds like it already may be linking against 
/usr/local/lib
where the current libSDL is, you should just be able to add the new lib dir
to the LD_LIBRARY_PATH env variable, and then run ldd on qemu to make
sure it's finding the right libraries. When you have the right LD_LIBRARY_PATH,
then it should be working for you.

  

Is to possible to have a staticly
linked version of libSDL in the qemu binaries?



There is an option for statically linked libSDL in the qemu binaries, 
  


Sounds funny.

and I tried to make sure I kept that intact for solaris in the configure
script.  


wow

Try it and see what happens.  
  


Not much.

Ben


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


  




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel


Re: [Qemu-devel] configure flag for compilation question..

2006-10-13 Thread Martin Bochnig
Ben Taylor wrote:

 Martin Bochnig [EMAIL PROTECTED] wrote: 
  

Ben Taylor wrote:



 Ishwar Rattan [EMAIL PROTECTED] wrote: 
 

  

Trying to compile qemu on amd64 based Solaris.

I do not have write permission to /usr/local subtree

./configure --libdir=other-path --prefix=not-ustlocal
is fine
but make always generates binaries that want to find
/usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).

What is the way out for this sticky point?
   



Manually add -L/usr/local/lib -R/usr/local/lib 

  

Rather -L/his/home/sdl_amd64/lib -R/his/home/sdl_amd64/lib



Yeah, that.  brain fart when I was typing that.

  

Because I doubt, an amd64 version of libSDL is currently present in
/usr/local/lib/amd64
(and he doesn't have w access).



Right. I knew what I meant, I just didn't type it right.

  

This method is btw not really new to me, see my posting from a few
hours ago:
http://www.opensolaris.org/jive/thread.jspa?threadID=15448tstart=0




to the Makefile for the link
phase so it will correctly add those paths to the library lookup.  If I had
a code base to look at this instance, I could tell you where.  You could
also add those flags to Makefile.target in the SOLARIS specific areas,
which would probably make more sense.

As Martin indicated, setting LD_LIBRARY_PATH may get you a running
binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.

Ben
 

  

LD_LIBRARY_PATH is the wrong answer for Solaris
  

???
---  Weak statement.



LD_LIBRARY_PATH is the wrong answer for Solaris.  It's great for
trying to fix problems like this when the app won't run with a particular
set of libraries, or you're testing with new libraries and you don't
want to recompile  (I've done this before).  Too many people use
it as a panacea for poorly compiled/configured Open source software.
In this case, he might just set the LD_LIBRARY_PATH and never
recompile it, even though it won't work if it uses the default LIB path.
  


No further comment, except this one:

bash-3.00# pwd
/opt/SUNWqemu/bin
bash-3.00# ls -al
total 676
dr-xr-xr-x   5 root bin 1024 Oct 14 06:26 .
drwxr-xr-x   5 root bin  512 Oct 14 06:26 ..
lrwxrwxrwx   1 root root   9 Oct 14 06:26 JQEMU.jar - jqemu.jar
lrwxrwxrwx   1 root root  10 Oct 14 06:26 JQEMU.jnlp -
jqemu.jnlp
lrwxrwxrwx   1 root root  20 Oct 14 06:26
SWING-LAYOUT-1.0.jar - swing-layout-1.0.jar
-r-xr-xr-x   1 root bin   48 Oct 14 03:23 jqemu-launcher-gui
-r-xr-xr-x   1 root bin   150854 Oct 14 03:30 jqemu.jar
-r-xr-xr-x   1 root bin  524 Oct 14 03:32 jqemu.jnlp
lrwxrwxrwx   1 root root  18 Oct 14 06:26 qemu -
./sparcv8plus/qemu
lrwxrwxrwx   1 root root  22 Oct 14 06:26 qemu-img -
./sparcv8plus/qemu-img
lrwxrwxrwx   1 root root  29 Oct 14 06:26 qemu-system-586 -
./sparcv8plus/qemu-system-586
lrwxrwxrwx   1 root root  29 Oct 14 06:26 qemu-system-686 -
./sparcv8plus/qemu-system-686
lrwxrwxrwx   1 root root  29 Oct 14 06:26 qemu-system-arm -
./sparcv8plus/qemu-system-arm
lrwxrwxrwx   1 root root  30 Oct 14 06:26 qemu-system-mips
- ./sparcv8plus/qemu-system-mips
lrwxrwxrwx   1 root root  32 Oct 14 06:26 qemu-system-mipsel
- ./sparcv8plus/qemu-system-mipsel
lrwxrwxrwx   1 root root  29 Oct 14 06:26 qemu-system-ppc -
./sparcv8plus/qemu-system-ppc
lrwxrwxrwx   1 root root  31 Oct 14 06:26 qemu-system-sparc
- ./sparcv8plus/qemu-system-sparc
lrwxrwxrwx   1 root root  32 Oct 14 06:26 qemu-system-x86_64
- ./sparcv8plus/qemu-system-x86_64
-r-xr-xr-x   1 root bin 1591 Oct 14 00:00 sdl-config
dr-xr-xr-x   2 root bin  512 Oct 14 06:26 sparcv7
dr-xr-xr-x   2 root bin  512 Oct 14 06:26 sparcv8
dr-xr-xr-x   2 root bin  512 Oct 14 06:26 sparcv8plus
-r-xr-xr-x   1 root bin   140545 Oct 14 03:30 swing-layout-1.0.jar
-r-xr-xr-x   1 root bin  332 Oct 14 05:39 test-qemu
-r-xr-xr-x   1 root bin  252 Oct 14 05:40 test-qemu-system-arm
-r-xr-xr-x   1 root bin  887 Oct 14 04:49 test-qemu-system-mips
-r-xr-xr-x   1 root bin  319 Oct 14 04:54 test-qemu-system-sparc
bash-3.00# ldd */qemu-system-mips|grep SDL
libSDL-1.2.so.0 =   /opt/SUNWqemu/lib/sparcv7/libSDL-1.2.so.0
libSDL-1.2.so.0 =   /opt/SUNWqemu/lib/sparcv8/libSDL-1.2.so.0
libSDL-1.2.so.0 =  
/opt/SUNWqemu/lib/sparcv8plus/libSDL-1.2.so.0
bash-3.00# ldd */qemu-system-mips|grep libz
libz.so =   /opt/SUNWqemu/lib/sparcv7/libz.so
libz.so =   /opt/SUNWqemu/lib/sparcv8/libz.so
libz.so =   /opt/SUNWqemu/lib/sparcv8plus/libz.so
bash-3.00# uname -a
SunOS mb1x-ws1 5.11 snv_41 sun4u sparc SUNW,Sun-Fire-280R
bash-3.00# isainfo -v
64-bit sparcv9 applications
vis2 vis
32-bit sparc applications
vis2 vis v8plus div32 mul32

[Qemu-devel] SUNWqemu-0.8.2, REV=2006.10.14-sol8-sparc-opt.pkg released

2006-10-13 Thread Martin Bochnig
Martin Bochnig wrote:

Hello,

uploading gdiff and sparc-pkg to www.martux.org/qemu/RELEASES/sparc and
to the opensolaris site.
In a few minutes.
  



Ouch, file too big:

File 1 (SUNWqemu-0.8.2,REV=2006.10.14-sol8-sparc-opt.pkg.gz) was
ignored. The file size is 28080k, which exceeds the maximum size of 15360k.
Cannot be uploaded to http://opensolaris.org/os/project/qemu/downloads


Please download the file(s) from
http://www.martux.org/qemu/RELEASES/sparc/
http://www.martux.org/qemu/RELEASES/sparc/SUNWqemu-0.8.2,REV=2006.10.14-sol8-sparc-opt.pkg.gz
http://www.martux.org/qemu/RELEASES/sparc/qemu-0.8.2-solaris__20061002mon__EricL__versus__qemu-0.8.2-solaris__20061013fri__MB.gdiff
http://www.martux.org/qemu/RELEASES/sparc/qemu-0.8.2__default_FabriceB__versus__qemu-0.8.2-solaris__20061013fri__MB.gdiff
for now.

See the diffs for added features.
Attention: IDE-Patch is derived from old IDE patch written by
grand-master Juergen Keil, who once achieved the major part of porting
QEMU to Solaris (!) back in 2004 .

He submitted that ide.c patch over a year ago, but it never made it into
CVS for some odd reason.


Regards

--
Martin Bochnig
http://www.martux.org/RELEASES/x86_and_x64/DVD/  (amd64)
http://www.genunix.org/distributions/martux/marTux_0.2/(sparcv9)

Generating x86 pkg till Sunday.
(port down to Sol8-i386 has to be polished up)


Regards,
Martin

  




___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel