From: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>
To: parisc-linux@lists.parisc-linux.org
Cc: baldric-exec@baldric.uwo.ca
Subject: [parisc-linux] testandset
Date: Thu, 20 Sep 2001 21:12:31 -0400 [thread overview]
Message-ID: <20010920211231.C24352@megatonmonkey.net> (raw)
parisc,
Trying to build glibc-2.2.4 on my 712/60
The build eventually halts because of the undefined "testandset"
---
/root/glibc_build/glibc-2.2.4/hppa-linux/obj/elf/ld.so.1: undefined reference to `testandset'
collect2: ld returned 1 exit status
make[4]: *** [/root/glibc_build/glibc-2.2.4/hppa-linux/obj/libio/tst_swscanf] Error 1
---
I've read all the docs for dpkg-dev, and yet the glibc debian stuff behaves
slightly different.
a) Unpack glibc 2.2.4, linux-threads, db1-add-on.
b) Patch to 2.2.4-1
c) Needed to comment hppa stuff back into 0list
d) Removed dl-fptr stuff from the hppa.dpatch (for now)
= Added morally equivalent changes to locking macro in ./sysdeps/ia64/dl-fptr.c
= testandset->try_lock
= Though I'm scratching my head at hppa/dl-fptr.c?
= Why is the ia64 stuff being touched anyway?
e) Packed it all back up as tar.bz2 (./debian rules seems to call for this)
f) Placed the tar.bz2's in the glibc-2.2.4 directory (so that they can be unpacked)
f) export LINUX_SOURCE=/usr/src/linux (no kernel-headers pakcage yet)
g) dpkg-buildpackage -uc -b -d (from within XXX/glibc-2.2.4)
glibc is almost as magical as the woman in the chair beside me watching
me type this email.
Debian has a ./rules section ... women don't :}
Any thoughts hackers?
Would you like the full dpkg-buildpackage log?
c.
next reply other threads:[~2001-09-21 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 1:12 Carlos O'Donell Jr. [this message]
2001-09-21 15:17 ` [parisc-linux] testandset Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2001-09-21 15:37 Carlos O'Donell Jr.
2001-09-21 15:42 ` Matthew Wilcox
2001-09-21 16:10 ` Carlos O'Donell Jr.
2001-09-21 15:58 Carlos O'Donell Jr.
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=20010920211231.C24352@megatonmonkey.net \
--to=carlos@megatonmonkey.net \
--cc=baldric-exec@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.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