Re: [microblaze-uclinux] uClinux Dhrystone option

[mcnernbm@xxxxxxxxxxxxxxxxx]

John,
Ok I fixed my makefiel to amtch your
posted one below but now when I build everythign goes ok but when I type
dhrystone once I login I get the following message:
BINFMT_FLAT: bad magic/rev (0x1010100,
need 0x4)
BINFMT_FLAT: bad magic/rev (0x1010100,
need 0x4)
ELF: not found

So what am I doing wrong now?  

Also I have been getting the follwoing message to while it is running:
init: /bin/inetd respawning too fast

But it still lets me run and move around
throught the directories even with that coming up
Thanks
Brett

John Williams <jwilliams@itee.uq.edu.au>
Sent by: owner-microblaze-uclinux@itee.uq.edu.au

04/24/2005 06:07 AM

Please respond to
microblaze-uclinux@itee.uq.edu.au

To	microblaze-uclinux@itee.uq.edu.au
cc
Subject	Re: [microblaze-uclinux] uClinux Dhrystone option

Hi Brett,

mcnernbm@notes.udayton.edu wrote:

> After getting a kernel to succesfully build I tried to build the same
> kernel with the dhrystone option enabled.  But I get the following
error 
> when I run make.  
> 
> make[2] Entering directory '/rot/uClinux-dist/user/dhrystone'
> make[2] *** No rule to make target 'romfs'. Stop.
> make[2] Leaving directory '/root/uClinux-dist/user/dhrystone'
> make[1] *** [romfs] Error 2
> make[1] Leaving directory '/root/uClinux-dist/user'
> make: *** [romfs] Error 1
> 
> Not sure why it is doing this or what i need to do to make this.

Sounds like a broken copy of the makefile.  Start by looking at 
uClinux-dist/user/dhrystone/Makefile... here's what mine looks like:

EXEC = dhrystone
OBJS = dhry_1.o dhry_2.o

CFLAGS += -DNO_PROTOTYPES=1

all: $(EXEC)

$(EXEC): $(OBJS)
         $(CC) $(LDFLAGS) -o $@ $(OBJS) $(LIBM) $(LDLIBS)

romfs:
         $(ROMFSINST) /bin/$(EXEC)

clean:
         -rm -f $(EXEC) *.elf *.gdb *.o

$(OBJS): dhry.h


If yours looks different, it's probably broken, just grab a fresh copy
via a CVS update or whatever.

If it looks like that, make sure it's not munged with CR/LF pairs or 
similar, as can happen if you pull source code via a windows box.

Not sure what else to suggest, this should just work, and usually does.

Regards,

John


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/