Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130329111050.GA4991@gremlin.ru>
Date: Fri, 29 Mar 2013 15:10:50 +0400
From: gremlin@...mlin.ru
To: owl-dev@...ts.openwall.com
Subject: embedded Owl - glibc/i586 build error

Colleagues, does anyone have an idea of how to build Owl for this CPU:

processor       : 0
vendor_id       : CentaurHauls
cpu family      : 6
model           : 7
model name      : VIA Samuel 2
stepping        : 3
cpu MHz         : 400.935
cache size      : 64 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu de tsc msr cx8 mtrr pge mmx 3dnow
bogomips        : 802.84

I tried setting ARCHITECTURE=i386 in buildworld.conf together with
passing "-march=i486 -mtune=i586" to %optflags (via ~build/.rpmmacros),
and everything went fine except the only package. Alas, that's glibc:

make[3]: Entering directory `/usr/src/world/rpm-work-4/BUILD/glibc-2.3.6/nptl'
In file included from ../nptl/sysdeps/unix/sysv/linux/libc-lowlevellock.c:21:0:
../nptl/sysdeps/unix/sysv/linux/lowlevellock.c:28:1:
error: conflicting types for '__lll_lock_wait'
../nptl/sysdeps/unix/sysv/linux/i386/lowlevellock.h:226:12:
note: previous declaration of '__lll_lock_wait' was here

I tried patching lowlevellock.h to solve the conflict, but that only
resulted in:

make[3]: *** No rule to make target `/usr/src/world/rpm-work-1/BUILD
/glibc-2.3.6/build-i386-linux/nptl/pthread_spin_trylock.o', needed by
`lib-noranlib'. Stop.

For i686, it builds just fine. WTF and WTD? :-/


-- 
Alexey V. Vissarionov aka Gremlin from Kremlin <gremlin ПРИ gremlin ТЧК ru>
GPG key ID: 0xEF3B1FA8, keyserver: hkp://subkeys.pgp.net
GPG key fingerprint: 8832 FE9F A791 F796 8AC9 6E4E 909D AC45 EF3B 1FA8

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.