[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140511171408.GA27908@cachalot>
Date: Sun, 11 May 2014 21:14:08 +0400
From: Vasily Kulikov <segoon@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: trying to build Owl for Raspberry Pi: rpmquery
--specfile
On Sun, May 11, 2014 at 21:03 +0400, croco@...nwall.com wrote:
> Anyway, now it looks like this:
>
> # build@...pi ~$ make buildworld
> # test -d native/Owl/build || make checkout
> # ln -s native/Owl/build/{*.conf,.rpm*} . 2> /dev/null || :
> # BRANCH=Owl PACKAGE= native/Owl/build/buildworld.sh
> # 00:06:54: Detecting version of RPM
> # 00:06:54: It's RPM4, using different binaries for different tasks
> # 00:06:54: Removing stale temporary files
> # 00:06:54: Sanity check
> # 00:06:54: #1: Scanning native
> # warning: line 25: prereq is deprecated: PreReq: owl-control >= 0.4,
> # owl-control < 2.0
> # 00:06:55: #1: Building SimplePAMApps
> # 00:06:55: #1: Failed SimplePAMApps
> # 00:06:56: #1: Building SysVinit
> # 00:07:25: #1: Failed SysVinit
> # warning: line 22: prereq is deprecated: PreReq: /sbin/install-info, grep,
> # coreutils >= 5.3.0, sed >= 4.0.9
> # 00:07:25: #1: Building acct
> # 00:07:26: #1: Failed acct
> # warning: line 17: prereq is deprecated: PreReq: /sbin/install-info
> # warning: line 17: prereq is deprecated: PreReq: /sbin/install-info
> # 00:07:26: #1: Building autoconf
> # 00:07:27: #1: Failed autoconf
>
> and so on. Well, as far as I can tell, all this is described in BUILD.txt
> with a short phrase <<Building on another GNU/*/Linux system is sometimes
> possible, but tricky and requires that you slowly produce an Owl system
> with multiple iterations of "make buildworld" and "make installworld".>>
> So, any help with further tricks of that 'tricky building'? I'd love more
> documentation to read, but it seems that none exists.
Please post several log files from /usr/src/world/logs/$package (the
last lines from it with 'failed' or 'error' strings of compiler/building
scripts output). It is not obvious what's missing/broken for your arch.
Also several packages have scripts for specific architectures only.
In this case you should investigate whether the package or building
scripts have arch-specific things and try to fix it. Probably simple
addition of your arch into *Arch might fix it.
$ grep ExclusiveArch native/Owl/packages/*/*spec
native/Owl/packages/cdrkit/cdrkit.spec:ExclusiveArch: %ix86 x86_64
native/Owl/packages/dev86/dev86.spec:ExclusiveArch: %ix86 x86_64
native/Owl/packages/dmidecode/dmidecode.spec:ExclusiveArch: %ix86 x86_64
native/Owl/packages/elftoaout/elftoaout.spec:ExclusiveArch: sparc sparcv9 sparc64
native/Owl/packages/kernel/kernel.spec:ExclusiveArch: i686 x86_64
native/Owl/packages/lilo/lilo.spec:ExclusiveArch: %ix86 x86_64
native/Owl/packages/ltrace/ltrace.spec:ExclusiveArch: %ix86 x86_64 sparc sparcv9
native/Owl/packages/owl-cdrom/owl-cdrom.spec:ExclusiveArch: %ix86 x86_64
native/Owl/packages/prtconf/prtconf.spec:ExclusiveArch: sparc sparcv9 sparc64
native/Owl/packages/setarch/setarch.spec:ExclusiveArch: %ix86 x86_64 sparc sparcv9 sparc64 ppc ppc64 mips mips64 ia64 s390 s390x
native/Owl/packages/silo/silo.spec:ExclusiveArch: sparc sparcv9 sparc64
native/Owl/packages/syslinux/syslinux.spec:ExclusiveArch: %ix86 x86_64
--
Vasily
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.
