ext-inst.cc Input/output error

ext-inst.cc Input/output error

[Shaun Jackman]

I'm building gcc for arm-wince-pe. I'm getting an "Input/output error"
when compiling ext-inst.cc. I've built this tool-chain before, and I
don't think I've done anything different. I have free disk space, and
this disk is behaving fine. I've removed all the build directories and
tried again, but the same error on the same file pops up.

Please cc me in your reply. Thanks,
Shaun

gcc 3.3.1
binutils 2.14
Linux 2.6.8.1

/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/gcc/xgcc
-shared-libgcc -B/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/gcc/
-nostdinc++ -L/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/src
-L/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/src/.libs
-nostdinc -B/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/newlib/
-isystem /home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/newlib/targ-include
-isystem /home/sjackman/work/pathway/toolchain/pocketpc/gcc/gcc-3.3.1/newlib/libc/include
-B/opt/pocketpc/arm-wince-pe/bin/ -B/opt/pocketpc/arm-wince-pe/lib/
-isystem /opt/pocketpc/arm-wince-pe/include -nostdinc++
-I/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/include/arm-wince-pe
-I/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/include
-I../../../../gcc-3.3.1/libstdc++-v3/libsupc++
-I../../../../gcc-3.3.1/libstdc++-v3/libmath -g -O2
-fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings
-fdiagnostics-show-location=once -c
../../../../gcc-3.3.1/libstdc++-v3/src/ext-inst.cc -o ext-inst.o
In file included from
/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/include/ext/ropeimpl.h:54,
                 from
/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/include/ext/stl_rope.h:2497,
                 from
/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/include/ext/rope:60,
                 from ../../../../gcc-3.3.1/libstdc++-v3/src/ext-inst.cc:34:
/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/include/ext/numeric:67:19:
/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/include/numeric:
Input/output error
make[5]: *** [ext-inst.lo] Error 1
make[5]: Leaving directory
`/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince-pe/libstdc++-v3/src'

RE: ext-inst.cc Input/output error

[Dave Korn]

> -----Original Message-----
> From: gcc-owner On Behalf Of Shaun Jackman
> Sent: 14 September 2004 16:14

> I'm building gcc for arm-wince-pe. I'm getting an "Input/output error"
> when compiling ext-inst.cc. I've built this tool-chain before, and I
> don't think I've done anything different. I have free disk space, and
> this disk is behaving fine. I've removed all the build directories and
> tried again, but the same error on the same file pops up.

  Very hard to tell from here; unfortunately the error message isn't
terribly informative.  For a start, we can't be really sure whether it's an
error when reading the input file, or an error when writing the temporary
preprocessed .i file, or conceivably an i/o error could be returned by a
mmap operation that fails, or who knows what.

  Also, the i/o error might not be to do with disk space, or bad sectors; it
could be a permissions problem.  (I've seen lots of software report 'io
error' or 'file not found' when in fact the file exists but the user/app
doesn't have the appropriate access perms).

  So, have you tried "cat
/home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince
-pe/libstdc++-v3/include/numeric" to see if you can access it from a shell?
And have you checked the perms on it with "ls -l"?  You might be able to run
the compile under strace to see what actual i/o call is failing.  Or you
might get some useful information by adding "-v" to the command line to see
each of the subcommand lines and then running the individual stages of
preprocess, compile, assemble separately.  You could also try adding
"--save-temps" to the build command line; if that fixes it, then you should
suspect that you don't have sufficient perms to write to /tmp.

  That's about all I can manage in off-the-top-of-my-head guesses for now.
Hope it helps.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

Re: ext-inst.cc Input/output error [RESOLVED]

[Shaun Jackman]

Thanks for your extensive reply! It was apparently some problem with
the source tree, although I still don't know exactly what. It wasn't a
permissions problem, because I was able to 'rm -f' the entire tree as
the user. I unpacked the sources and rebuilt without trouble this
time.

Cheers,
Shaun


>   Very hard to tell from here; unfortunately the error message isn't
> terribly informative.  For a start, we can't be really sure whether it's an
> error when reading the input file, or an error when writing the temporary
> preprocessed .i file, or conceivably an i/o error could be returned by a
> mmap operation that fails, or who knows what.
> 
>   Also, the i/o error might not be to do with disk space, or bad sectors; it
> could be a permissions problem.  (I've seen lots of software report 'io
> error' or 'file not found' when in fact the file exists but the user/app
> doesn't have the appropriate access perms).
> 
>   So, have you tried "cat
> /home/sjackman/work/pathway/toolchain/pocketpc/gcc/build-gcc-3.3.1/arm-wince
> -pe/libstdc++-v3/include/numeric" to see if you can access it from a shell?
> And have you checked the perms on it with "ls -l"?  You might be able to run
> the compile under strace to see what actual i/o call is failing.  Or you
> might get some useful information by adding "-v" to the command line to see
> each of the subcommand lines and then running the individual stages of
> preprocess, compile, assemble separately.  You could also try adding
> "--save-temps" to the build command line; if that fixes it, then you should
> suspect that you don't have sufficient perms to write to /tmp.
> 
>   That's about all I can manage in off-the-top-of-my-head guesses for now.
> Hope it helps.
> 
>     cheers,
>       DaveK

RE: ext-inst.cc Input/output error [RESOLVED]

[Dave Korn]

> -----Original Message-----
> From: gcc-owner On Behalf Of Shaun Jackman
> Sent: 14 September 2004 19:12
> To: gcc
> Subject: Re: ext-inst.cc Input/output error [RESOLVED]
> 
> Thanks for your extensive reply! It was apparently some problem with
> the source tree, although I still don't know exactly what. It wasn't a
> permissions problem, because I was able to 'rm -f' the entire tree as
> the user. I unpacked the sources and rebuilt without trouble this
> time.
> 
> Cheers,
> Shaun


  Quite possibly you may have accidentally run "./configure" in the source
dir.  Gcc doesn't support building in objdir==srcdir [*], and inadvertantly
configuring in the source dir is known to leave traces behind which can
interfere with subsequent build attempts.

  Anyway, glad it's sorted out.


    cheers, 
      DaveK

[*] well, sometimes it does and sometimes it doesn't, but as the docs say,
"we highly recommend against" doing this, as it "doesn't get a lot of
testing".....
-- 
Can't think of a witty .sigline today....