Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060831202005.4c25bfff@shadow>
Date: Thu, 31 Aug 2006 20:20:05 +0400
From: "Melekhov Alexandre A." <amel@...ru>
To: owl-users@...ts.openwall.com
Subject: Re: perl at x86-64

Hello Solar Designer.

On Thu, 31 Aug 2006 19:29:46 +0400, you wrote about "Re: [owl-users] perl at x86-64":

> On Thu, Aug 31, 2006 at 03:58:23PM +0400, Melekhov Alexandre A. wrote:
> > -Dinstallprefix=/usr/src/world/rpm-work-1/buildroot/usr
> > -Dprefix=/usr 
> 
> This was a bug introduced in the Perl package in Owl-current
> (post-2.0), and it got fixed in June.  Unfortunately (for you), the
> pre-built x86-64 packages of Owl-current were not being updated
> frequently enough - so they were from a May snapshot until just a few
> days ago.
> 
> Please update to the packages currently on our FTP mirrors - and the
> problem should be gone.
 
All OK. Thanks a lot!

BTW untill your answer I tried to buildworld on 64-bit machine and got a lot of errors like this:

x64!build:~$ make clean && make buildworld
test -d RPMS && rm -f RPMS/* || :
test -d SRPMS && rm -f SRPMS/* || :
test -d archives && rm -f archives/* || :
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
19:39:47: Detecting version of RPM
19:39:47: It's RPM4, using different binaries for different tasks
19:39:47: Removing stale temporary files
hostname: Unknown host
19:39:47: Sanity check
19:39:47: #1: Scanning native
19:39:47: #2: Scanning native
19:39:47: #2: Building SysVinit
19:39:47: #1: Building SimplePAMApps
19:39:47: #2: Failed SysVinit
19:39:47: #1: Failed SimplePAMApps
[..]

Receipt to buildworld takek from "http://openwall.com/Owl/BUILD.shtml"

-- 
===========================
Best regards, SKYDIVER-RIPN
amel@...ru

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.