From: "Ringeman, Tim" <tim_ringeman@gilbarco.com>
Subject: Problem with compiling and linking separately
Date: Mon, 19 Jul 1999 14:07:34 -0400 [thread overview]
Message-ID: <199907191808.OAA14312@hoover.gilbarco.com> (raw)
I am running the embedded-2.2.5 kernel on a MBX860 board and using
http://members.home.net/mmporter/binutils-powerpc-linux-2.9.1.0.15-2.i386.rp
m
http://members.home.net/mmporter/egcs-powerpc-linux-1.1.1-2.i386.rpm
ftp://sourceware.cygnus.com/pub/glibc/glibc-2.1.tar.gz
ftp://sourceware.cygnus.com/pub/glibc/glibc-linuxthreads-2.1.tar.gz
ftp://ftp.funet.fi/pub/gnu/funet/glibc-crypt-2.1.tar.gz
When I try to compile and link seperately I get the following errors:
[root@ngdtst06 bin]# powerpc-linux-gcc -c hello.c
[root@ngdtst06 bin]# powerpc-linux-ld hello.o
powerpc-linux-ld: warning: cannot find entry symbol _start; defaulting to
01800074
hello.o: In function `main':
hello.o(.text+0x20): undefined reference to `printf'
[root@ngdtst06 bin]# powerpc-linux-ld hello.o -lc
powerpc-linux-ld: warning: cannot find entry symbol _start; defaulting to
01800188
[root@ngdtst06 bin]# powerpc-linux-ld hello.o -lc -static
powerpc-linux-ld: warning: cannot find entry symbol _start; defaulting to
01800188
When I link against the shared libraries as such:
[root@ngdtst06 bin]# powerpc-linux-ld hello.o -lc -shared
it links but when I try to run it on the board, it hangs.
Any idea how I could get this to work?
Thanks,
Tim
Tim Ringeman
Gilbarco Inc.
Telephone 336-547-5946
e-mail: tim_ringeman@gilbarco.com
http://www.gilbarco.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-07-19 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-19 18:07 Ringeman, Tim [this message]
1999-07-19 18:27 ` Problem with compiling and linking separately David Edelsohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199907191808.OAA14312@hoover.gilbarco.com \
--to=tim_ringeman@gilbarco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).