Compiler error

[M.Caggiano]

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?
Many many thanks in advance.

[Mark McIntyre]

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.

--
Mark McIntyre

CLC FAQ <http://c-faq.com/>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>

[=?UTF-8?q?Harald_van_D=C4=B3k?=]

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.

[Walter Roberson]

In article <cc**************************@cache3.tilbu1.nb.hom e.nl>,
=?UTF-8?q?Harald_van_D=C4=B3k?= <tr*****@gmail.comwrote:

>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

>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,

I would agree. "Error 1" is make's typical error report after
a problem in the previous step, whether that step be a compile or link.
It is what "make" reports for the majority of situations in which
the previous step returned a non-success error code. The actual
problem would have appeared above that.
--
"No one has the right to destroy another person's belief by
demanding empirical evidence." -- Ann Landers

[Richard Heathfield]

Mark McIntyre said:

<snip>

This looks more like a linker error, by the way - nothing to do with C.

Linking is Translation Phase 8, a very important part of the translation
process for C programs. It is lots to do with C.

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999

[Mark McIntyre]

Richard Heathfield wrote:

Mark McIntyre said:

<snip>

>This looks more like a linker error, by the way - nothing to do with C.

Linking is Translation Phase 8, a very important part of the translation
process for C programs. It is lots to do with C.

Read what I wrote more carefully.

While "linking" is something to do with C, the linker is not. The linker
is a language-neutral tool that performs the action of linking.

--
Mark McIntyre

CLC FAQ <http://c-faq.com/>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>

[Mark McIntyre]

M.Caggiano wrote:

The only error of the function is that.

You typed
gcc myfile.c

and that was the only output?????

I don't know whether to also think because the message is enough
vague.

You need to post more detail...

--
Mark McIntyre

CLC FAQ <http://c-faq.com/>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>

[Robert Latest]

M.Caggiano wrote:

Thank's for your answer.
This is the c code:

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <winsock.h>
#include <windows.h>

And these few lines are enough to see that what you're having is not really
a C problem but (possibly) a Windows API problem, and is therefore off-topic
in this newsgroup.

Go to a newsgroup concerned with Windows networking programming, where your
question is on-topic. We can't realy help you here.

robert