Running simple C program

[Sim085]

Hello,

I am trying to learn some C/C++ on Amiga. However I go stuck at the very beginning. I have taken the following the time I learn C on a windows machine;

#include <stdio.h>

int main(){
    
    printf("Hello World");
    return 0;
}

However when I run the make command I get the following error:

"Error 21" and "Reference to undefined symbol ___v0printf".

What am I doing wrong?

[emufan]

I guess more info is needed. which compiler are you using?
maybe attach the makefile

#1) with just this small source code, you may build it without a makefile:

gcc hello.c -o hello.exe

that's easier than updating the Makefile with any new source file.

#2) if you are using vbcc, here are some examples

[Sim085]

Yes, I did check those examples and they do work. I am using vbcc. However why the simple printf call doesn't work?

My make file looks as follows (exactly as the one in the link):

CC=vc
LDFLAGS=-nostdlib

HELLO_EXE=hello
HELLO_OBJS=hello.o

all: $(HELLO_EXE)

$(HELLO_EXE) : $(HELLO_OBJS) 
    $(CC) $(LDFLAGS) -nostdlib -o $(HELLO_EXE) $(HELLO_OBJS)

%.o : %.c
   $(CC) -c -o $@ $<

That said running vc or gcc or vbcc from Shell returns Unknown command.

Originally Posted by emufan

I guess more info is needed. which compiler are you using?
maybe attach the makefile

#1) with just this small source code, you may build it without a makefile:

gcc hello.c -o hello.exe

that's easier than updating the Makefile with any new source file.

#2) if you are using vbcc, here are some examples

[emufan]

you are not alone with that error:

vc -c -o hello.o hello.c
vc -nostdlib -nostdlib -o hello hello.o
hello.o: In "_main":
Error 21: hello.o (CODE+0x6): Reference to undefined symbol ___v0printf.
/opt/m68k-amigaos/bin/vlink -bamigahunk -x -Bstatic -Cvbcc -nostdlib "hello.o"  
 -s -Rshort -L/opt/m68k-amigaos/m68k-amigaos/vbcc/lib -L...vbcc/include -o hello failed
make: *** [Makefile:10: hello] Error 1

with gcc it does build this way:

m68k-amigaos-gcc.exe -noixemul hello.c -o hello.exe

need to check vbcc in what linker lib it provides the printf function.

#1) replace -nostdlib , with -stdlib:

CC=vc
LDFLAGS=-stdlib

HELLO_EXE=hello
HELLO_OBJS=hello.o

all: $(HELLO_EXE)

$(HELLO_EXE) : $(HELLO_OBJS) 
	$(CC) $(LDFLAGS) -stdlib -o $(HELLO_EXE) $(HELLO_OBJS)

%.o : %.c
	$(CC) -c -o $@ $<

so it does build

[ajk]

You have "-nostdlib" in the Makefile. But printf() is part of the standard library and now there is no implementation for it, which is why you get the error.

Either build with the standard library or use the Amiga API for printing text.

[Sim085]

So obviously I am just into this, my only experience of C development is a little from Windows. What is the advantage of using one or the other?

Originally Posted by ajk

You have "-nostdlib" in the Makefile. But printf() is part of the standard library and now there is no implementation for it, which is why you get the error.

Either build with the standard library or use the Amiga API for printing text.

[ajk]

Well, it doesn't really matter for a Hello World type program. The Amiga API will be more efficient when coding a (complex) program specifically for the Amiga. But it will not be portable to other systems, if that is a concern. And of course you must seek Amiga specific advice rather than be able to follow any standard tutorials.

And of course you can use both the standard library and Amiga headers in the same program, as required. You'll find that there is a "windows.h" when coding for the Windows API and also POSIX headers for Linux/UNIX and so on.

[Sim085]

Thanks that really got me moving. I still have to familiarise myself and follow more tutorials but like this I can already write and run some of the basic stuff I learnt at school.

[phx]

Do not use Makefiles from somebody else when you don't know what all the options are doing in it.

Compiling a single source using the standard clib into an executable is as easy as typing:

vc +aos68k -o hello hello.c

(in case you are compiling for m68k)

[Sim085]

That is what I thought, from looking at the makefile script I can see it uses vc. However when I try it from Shell it gives me unknown command. I checked System:C and can only see make. No vc. I still can't figure how make executes vc.

Originally Posted by phx

Do not use Makefiles from somebody else when you don't know what all the options are doing in it.

Compiling a single source using the standard clib into an executable is as easy as typing:

vc +aos68k -o hello hello.c

(in case you are compiling for m68k)

[phx]

Originally Posted by Sim085

I checked System:C and can only see make. No vc. I still can't figure how make executes vc.

The vbcc binaries are in vbcc:bin, and when installed correctly the user-startup should add an assignment to C: like this:

assign >NIL: C: vbcc:bin ADD