From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Add -nodefaultlibs while compiling against klibc
Date: Mon, 08 Dec 2003 10:02:09 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107087791501623@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106978186702036@msgid-missing>
On Sunday 07 December 2003 22:55, Olaf Hering wrote:
>
> this gives me linker errors on ppc and ia64:
>
> tdb/tdb.o(.text+0x1092): In function `tdb_chainunlock_read':
> : undefined reference to `__umodsi3'
Does this help?
diff -Nru a/Makefile b/Makefile
--- a/Makefile Tue Nov 25 12:26:18 2003
+++ b/Makefile Tue Nov 25 12:26:18 2003
@@ -124,7 +124,7 @@
-I$(INCLUDE_DIR)/bits$(BITSIZE) -I$(GCCINCDIR) -Iklibc/linux/include \
-D__KLIBC__
LIB_OBJS - LDFLAGS = --static --nostdlib -nostartfiles -nodefaultlibs
+ LDFLAGS = --static --nostdlib -nostartfiles -nodefaultlibs -lgcc
else
CRT0 LIBC
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-12-08 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 17:30 [PATCH] Add -nodefaultlibs while compiling against klibc Martin Hicks
2003-12-02 1:13 ` Greg KH
2003-12-07 21:55 ` Olaf Hering
2003-12-08 10:02 ` Arnd Bergmann [this message]
2003-12-08 15:38 ` Martin Hicks
2003-12-08 19:17 ` Olaf Hering
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=marc-linux-hotplug-107087791501623@msgid-missing \
--to=arnd@arndb.de \
--cc=linux-hotplug@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).