30.05.2012 02:46, solarflow99 wrote:
> oh, so I guess svn2080 was the last commit before switching to git, is
> svn not used at all anymore? I used to do a "svn co" to create a tar
> file from the latest release, i'll have to lookup how that is done
> with git.
Try
git archive -o dosemu.tar HEAD
oh, so I guess svn2080 was the last commit before switching to git, is
svn not used at all anymore? I used to do a "svn co" to create a tar
file from the latest release, i'll have to lookup how that is done
with git. Its almost time to make a F-17 package, which used -svn
in the name.
Thanks
29.05.2012 21:24, solarflow99 wrote:
> Hi, I had about 4 - 5 simple changes i'd like to commit to svn, since
dosemu uses git already.
> this is 1 time only and I don't want to risk messing anything up, what
> is the best way I can do this?
If you just have a random patch, you can post it here:
htt
Hi, I had about 4 - 5 simple changes i'd like to commit to svn, since
this is 1 time only and I don't want to risk messing anything up, what
is the best way I can do this?
Thanks,
--
Live Security Virtual Conference
Excl
Hi,
I managed to run the binary from RPMFusion and it indeed hung at the
place you debugged; I hope I fixed the problem with SVN #2058.
It could just be in the CFLAGS etc that are used on RPMFusion; the
character set list isn't initialized in a set order and the particular
order that is used ther
thanks for the pointers on this. It doesn't yield any obvious clues to me,
unless you can recognize something wrong from the output:
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/ld-linux.so.2...Reading symbols from
/usr/lib/debug/lib/ld-2.14.so.debug...done.
done.
Loaded symb
Hi,
you can just run dosemu (preferably with debug info on), then leave it
hanging and
do
gdb /path/to/dosemu.bin `pidof dosemu.bin`
bt
where /path/to is where the dosemu.bin is that you ran.
the backtrace should show where the process is hanging.
Bart
-
I'd have to assume it was a problem with the build system to make it hang
there like that, its wierd. Unless there's a missing dependancy, but then
it shouldn't even compile, here's what is pulled in in case anyone notices
something missing:
BuildRequires:bison
BuildRequires:flex
BuildRe
oh ya.. It seems to be a problem with package builds on rpmfusion, when I
rpmbuild on my own system it works. Strange.. Here is the strace output
anyways: Thanks guys..
# strace dosemu.bin
execve("/usr/bin/dosemu.bin", ["dosemu.bin"], [/* 46 vars */]) = 0
brk(0)
On 05.09.2011 20:57, Bart Oldeman wrote:
> Hi,
>
>> has anyone even tried svn 2053? does it work at all?
> it works fine here (i386, Debian testing with kernel 3.0).
>
works fine here too, amd64, Debian kernel 3.0, 3.1-rc4
Reinhard
---
Hi,
> has anyone even tried svn 2053? does it work at all?
it works fine here (i386, Debian testing with kernel 3.0).
I'm not sure why it hangs for you. Also in response to your previous
post, can you strace dosemu.bin instead of dosemu? And attach
boot.log?
Bart
--
has anyone even tried svn 2053? does it work at all?
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs
Has anyone noticed a problem with svn 2053 in Fedora 15 i686? It just hangs
at the command line, here is the tail end output of strace:
ioctl(0, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS,
{B38400 opost isig icanon echo ...}) = 0
fstat64(0, {st_mode=S_IFCHR|0620, st_rdev=make
13 matches
Mail list logo
