Skip to contentSkip to conversation

testandset

parisc-linux Carlos O'Donell Jr. 2 participants 2 messages Sep 21, 2001

lore
Share & tools
lore
#0 lore 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.

#1 lore raw
Quoted 11 lines · Carlos O'Donell Jr.

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?

because we're removing the testandset macro, replacing it with try_lock.

Quoted 1 line

e) Packed it all back up as tar.bz2 (./debian rules seems to call for this)

No, definitely not, I don't know why you think you need to do that.

Quoted 3 lines

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)

Here's what you ned to do:

dpkg-source -x *dsc
cd glibc-*
frob 0lists & hppa.dpatch as above
put a copy of the kernel includes in /usr/src/linux/include rather than setting LINUX_SOURCE
dpkg-buildpackage -B -a -rfakeroot

Signature · 1 line
Revolutions do not require corporate support.