[cfarm-users] having a bit of trouble with getting into the new netbsd and freebsd virtual machines

[CM Graff]

Hey Assaf and everyone!

I did discover a few things.

gcc300$ echo "int x = 0;" > example.c
gcc300$ cc --freestanding -nostdlib -static example.c
ld: warning: cannot find entry symbol _start; defaulting to 0000000000400078
gcc300$ ./a.out
-sh: Cannot execute ELF binary ./a.out

Making this simple freestanding binary results in the same issue.

When doing the same on my linux box, the a.out runs and the binary
simply segfaults (but does run!).

I did try the new clang package and it results in the same issue.
Thank you for installing that Assaf! It will come in handy quite soon.

I'll take some of these questions to the netbsd developers and try to
get to the bottom of this.

Thanks again!

Graff




On 10/6/18, Assaf Gordon <assafgordon at gmail.com> wrote:
> Hello Graff,
>
> On 06/10/18 09:02 PM, CM Graff via cfarm-users wrote:
>> To follow up, I think that the problem is a bit more complex. I am
>> guessing now that there is a Linux/ELF compat mechanism somewhere in
>> the default compiler search path. I think for hlibc to work with
>> NetBSD I'll have to research how this all works, or perhaps even
>> specify a different binary format. Because I am redirecting the
>> compiler search paths to only look for hlibc's libc.a, crt1.o, crtn.o
>> and crti.o something is probably getting excluded. Open to
>> suggestions, but I am starting to think this is not a system
>> maintenance issue but something of a different nature having to do
>> with various less used compiler invocations.
>
> I know very little about the above, but note that:
>
> 1.
> gcc300 is NetBSD 7.1 - not yet upgraded to NetBSD 8.0.
> Not sure if there is a big difference.
> I do plan to upgrade in the near future.
>
> 2.
> I've just installed clang-5.0.2 on gcc300,
> perhaps using it instead of the (very old) gcc
> would make things easier to troubleshoot.
>
>
> regards,
>   - assaf
>
>
>