[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-tar] new/old extract problems with 6GB sparse file
From: |
Joerg Delker |
Subject: |
Re: [Bug-tar] new/old extract problems with 6GB sparse file |
Date: |
Mon, 19 Jun 2006 00:07:01 +0200 |
User-agent: |
Thunderbird 1.5.0.2 (X11/20060516) |
Joerg,
thanks for the information.
That should get me going to extract the stack trace.
Unfortunately, star stubbornly refuses to compile here :-(
Even after RTFM... ;-)
BTW: Is it ok to discuss this here, or is there a seperate forum/mail
list for star?
With /usr/src/linux removed, the errors change to this:
...
==> MAKING DEPENDENCIES "star_unix.d"
In file included from /usr/include/asm/mpspec.h:8,
from /usr/include/asm-i486/smp.h:18,
from /usr/include/asm/smp.h:8,
from /usr/include/linux/smp.h:19,
from /usr/include/linux/percpu_counter.h:11,
from /usr/include/linux/ext2_fs_sb.h:20,
from /usr/include/linux/ext2_fs.h:20,
from star_unix.c:59:
/usr/include/asm-i486/mpspec.h:6:25: error: mach_mpspec.h: No such file
or directory
In file included from /usr/include/asm/smp.h:8,
from /usr/include/linux/smp.h:19,
from /usr/include/linux/percpu_counter.h:11,
from /usr/include/linux/ext2_fs_sb.h:20,
from /usr/include/linux/ext2_fs.h:20,
from star_unix.c:59:
/usr/include/asm-i486/smp.h:77:26: error: mach_apicdef.h: No such file
or directory
...
$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--program-suffix=-4.0 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-java-awt=gtk-default
--enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre
--enable-mpfr --disable-werror --with-tune=i686
--enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)
JD
Joerg Schilling wrote:
Joerg Delker <address@hidden> wrote:
>> Could you send a stack trace from the core?
> Uhh... I haven't dived into core analysis yet. Do you have short
> instructions how to retrieve that?
In UNIX just call adb <path to star> <path to core> and then type $c
otherwise you youle need to be happy with 'gdb' which helps less
call gdb <path to star> <path to core>
and then type "where"
You may like to call
smake clean smake COPXT=-g LDOPTX=-g
and create a new core
This is needed because gdb is too dumb to correctly show the function
arguments otherwise.
Note that the "real" star binary is called "star_fat"
>>> Any more hints?
>> The Linux Kernel guys don't like to fix the bugs/incnosistencies
>> in their include files. Try to rename /usr/src/linux
> You mean "rename" in the sense of "move out of the way"? Already
> tried that, but Gmake complains about missing files then: ...
> make[1]: *** No rule to make target
> `/usr/src/linux/include/linux/limits.h', needed by
> `OBJ/i686-linux-cc/tartest.o'. Stop. ...
See README.compile, you would needd to call 'smake depend' in order
to clear the old dependency list.
Jörg
- [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Delker, 2006/06/18
- Re: [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Schilling, 2006/06/18
- Re: [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Delker, 2006/06/18
- Re: [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Schilling, 2006/06/18
- Re: [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Delker, 2006/06/18
- Re: [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Schilling, 2006/06/18
- Re: [Bug-tar] new/old extract problems with 6GB sparse file,
Joerg Delker <=
- Re: [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Schilling, 2006/06/18
- Re: [Bug-tar] new/old extract problems with 6GB sparse file, Joerg Delker, 2006/06/18
Re: [Bug-tar] new/old extract problems with 6GB sparse file, Sergey Poznyakoff, 2006/06/19
Re: [Bug-tar] new/old extract problems with 6GB sparse file, Paul Eggert, 2006/06/19