[Qemu-devel] qemu and svn

[Qemu-devel] qemu and svn

[Dave Feustel]

I just checked the qemu source for 0.7.2 into svn
and then checked out the source. When I tried
to build the source, the build failed because the
symbolic link in i386-softmmu was no longer valid.
Any chance of not using links to files so this error
cannot happen? (Suggestions for workarounds 
welcome :-) ).

Thanks,
Dave Feustel
-- 
Tired of having to defend against Malware?
You know: trojans, viruses, SPYWARE, ADWARE, 
KEYLOGGERS, rootkits, worms and popups.
Then Switch to OpenBSD with a KDE desktop!!!
NOW with Virtual PC OS support via QEMU!

Re: [Qemu-devel] qemu and svn

[Paul Brook]

On Monday 14 November 2005 23:05, Dave Feustel wrote:
> I just checked the qemu source for 0.7.2 into svn
> and then checked out the source. When I tried
> to build the source, the build failed because the
> symbolic link in i386-softmmu was no longer valid.
> Any chance of not using links to files so this error
> cannot happen? (Suggestions for workarounds
> welcome :-) ).

The i386-softmmu directory is not part of the source tree. It is created by 
the build process, so should not be under version control.

Paul

Re: [Qemu-devel] qemu and svn

[Dave Feustel]

On Monday 14 November 2005 18:13, Paul Brook wrote:
> On Monday 14 November 2005 23:05, Dave Feustel wrote:
> > I just checked the qemu source for 0.7.2 into svn
> > and then checked out the source. When I tried
> > to build the source, the build failed because the
> > symbolic link in i386-softmmu was no longer valid.
> > Any chance of not using links to files so this error
> > cannot happen? (Suggestions for workarounds
> > welcome :-) ).
> 
> The i386-softmmu directory is not part of the source tree. It is created by 
> the build process, so should not be under version control.

I had attempted a build before I put the code in the repository.
I'll purge this repository and build another from freshly downloaded
code.
 
> Paul
> 

-- 
Tired of having to defend against Malware?
You know: trojans, viruses, SPYWARE, ADWARE, 
KEYLOGGERS, rootkits, worms and popups.
Then Switch to OpenBSD with a KDE desktop!!!
NOW with Virtual PC OS support via QEMU!

Re: [Qemu-devel] qemu and svn

[Dave Feustel]

On Monday 14 November 2005 18:13, Paul Brook wrote:
> On Monday 14 November 2005 23:05, Dave Feustel wrote:
> > I just checked the qemu source for 0.7.2 into svn
> > and then checked out the source. When I tried
> > to build the source, the build failed because the
> > symbolic link in i386-softmmu was no longer valid.
> > Any chance of not using links to files so this error
> > cannot happen? (Suggestions for workarounds
> > welcome :-) ).
> 
> The i386-softmmu directory is not part of the source tree. It is created by 
> the build process, so should not be under version control.
> 
> Paul

I created a new repository from a freshly downloaded qemu tarball
checked it out, configured
----------------
./configure \
--target-list=i386-softmmu \
--disable kqemu
----------------
 and  ran gmake. Got the following:
==============
/home/daf/Qemu/Qsrc}gmake
gcc -DQEMU_TOOL -Wall -O2 -g -fno-strict-aliasing  -g -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -o qemu-img qemu-img.c block.c block-cow.c block-qcow.c aes.c block-vmdk.c block-cloop.c block-dmg.c block-bochs.c block-vpc.c block-vvfat.c -lz
In file included from vl.h:68,
                 from qemu-img.c:24:
osdep.h:34: warning: `struct siginfo' declared inside parameter list
osdep.h:34: warning: its scope is only this definition or declaration, which is probably not what you want
=============
These errors are new. I don't yet understand why they are happening.

Dave
-- 
Tired of having to defend against Malware?
You know: trojans, viruses, SPYWARE, ADWARE, 
KEYLOGGERS, rootkits, worms and popups.
Then Switch to OpenBSD with a KDE desktop!!!
NOW with Virtual PC OS support via QEMU!

Re: [Qemu-devel] qemu and svn

[Dave Feustel]

On Monday 14 November 2005 19:02, Dave Feustel wrote:
> These errors are new. I don't yet understand why they are happening.
My mistake. I saw exactly these same errors while porting PETSc and MPICH2 to OpenBSD
and didn't realize until this morning that they were now occuring on a *different* project..
It looks like OpenBSD needs to add some header files to /usr/include.
I apologise for the noise I generated in my confusion.

Dave
-- 
Switch to Secure OpenBSD with a KDE desktop!!!
NOW with Virtual PC OS support via QEMU and
Beowulf clustering using PETSc and MPICH2!