From: Paul Furber <paulf@gam.co.za>
To: linux-assembly@vger.kernel.org
Subject: asmutils libc fun and games
Date: Fri, 17 May 2002 15:24:47 +0200 [thread overview]
Message-ID: <3CE5049F.5000405@gam.co.za> (raw)
Hello fellow asm heads,
I've discovered the joys of the asmutils boot disk and now want to make
it possible to include statically linked code written in C and the
asmutils libc library on the distro. But I can't get the static versions
working. Here's the problem:
In the Makefile (in asmutils-0.16/lib/) I have:
BUILD_STATIC = y
BUILD_SHARED = y
But when building the static test proggie I get:
gcc -D__CPU__=386 -Wall -O1 -m386 -g -D__NO_STRING_INLINES -fno-builtin
-nostartfiles -nostdlib -static -o test1-static test1.c libc_stub.o libc.a
libc.a(libc.o): In function `_start':
libc.o(.text+0x4): multiple definition of `_start'
libc_stub.o(.text+0x0): first defined here
collect2: ld returned 1 exit status
make: *** [test1] Error 1
If I comment out STUB_OBJS and remake the static portion, then some of
the static versions are compiled but output the __libc_banner file which
reads:
A r e y ou s i c k ?
To which I reply yes! :) I would like a tiny libc written in asmutils
that links statically so as to include some demo-style progs on the
bootdisk. Am Imissing the point of this libc? Even the shared libraries
that build correctly are dynamically linked to libNoVersion and GNU libc
when you ldd them. What's up with that?
Paul.
next reply other threads:[~2002-05-17 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 13:24 Paul Furber [this message]
2002-05-18 23:58 ` asmutils libc fun and games h-peter recktenwald
2002-05-30 17:51 ` asmutils - Linux 2.4.18 h-peter recktenwald
2002-09-13 8:09 ` Is this list dead? halfdead
2002-09-13 9:20 ` Frederic Marmond
2002-09-22 12:29 ` kernel vulnerabilities halfdead
2002-09-22 15:19 ` Robin Miyagi
2002-09-13 9:55 ` Is this list dead? lx
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=3CE5049F.5000405@gam.co.za \
--to=paulf@gam.co.za \
--cc=linux-assembly@vger.kernel.org \
/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).