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* pro
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
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
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
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
welc
