Re: Compiler error
- From: Keith Thompson <kst-u@xxxxxxx>
- Date: Sun, 03 Feb 2008 12:25:09 -0800
Harald van Dijk <truedfx@xxxxxxxxx> writes:
On Sun, 03 Feb 2008 15:28:42 +0000, Mark McIntyre wrote:
M.Caggiano wrote:
I've write a function without errors but i've this message after
compilation:
*** ["../Socket/Client/Client.o"] Error1
how can i resolve this problem?
Read the compiler / linker manual to find out what "error 1" is. This
looks more like a linker error, by the way - nothing to do with C.
Doesn't look like a linker error to me. It looks like there's an error
reported by make or a similar build tool in generating
../Socket/Client/Client.o, which is typically the job of the compiler,
not the linker. I don't know why the OP didn't bother to post an actually
useful error message though.
It's hard to tell, but most tools I've seen report the name of the
*input* file in an error message. If the error message referred to
"../Socket/Client/Client.c", I'd assume a compile-time error; given
the reference to "Client.o", it's probably a link-time error.
Though it's conceivable that there was an error *writing* Client.o.
(I'm also assuming that the ".o" suffix denotes an object file, the
output of the compiler; this is not 100% certain, but I think it's a
safe bet, especially given that the form of the path implies a
Unix-like system.)
--
Keith Thompson (The_Other_Keith) <kst-u@xxxxxxx>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
.
- Follow-Ups:
- Re: Compiler error
- From: Keith Thompson
- Re: Compiler error
- References:
- Compiler error
- From: M.Caggiano
- Re: Compiler error
- From: Mark McIntyre
- Re: Compiler error
- From: Harald van Dijk
- Compiler error
- Prev by Date: Re: xmalloc string functions
- Next by Date: Re: xmalloc string functions
- Previous by thread: Re: Compiler error
- Next by thread: Re: Compiler error
- Index(es):
Relevant Pages
|