From owner-freebsd-current@FreeBSD.ORG Mon Jun 21 19:20:46 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 278E9106566B; Mon, 21 Jun 2010 19:20:46 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C50448FC08; Mon, 21 Jun 2010 19:20:45 +0000 (UTC) Received: by iwn7 with SMTP id 7so4673943iwn.13 for ; Mon, 21 Jun 2010 12:20:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=S4WUBFhZMt/iqt9493XkEWI3azEhoKeJeyHrHmtR4Eo=; b=cy1waM0kRvwNXpOm3eKbRwR1+PAZdenFiSWEqWVbmVTP7PBcJftGQv7ke6n6Dy5VLk U97hOusy2Lzjpa3MpU5WG91EvCH3OEXSQQ+MnaXsTjU5ZACyQgJsVfxs1drQV5EASfNR ZwybRFk0zEFmLFDdPoQhKeJwxcQiccE1lRW78= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=efJZz5njI4SQs4JERBxK2M2OeEiBQZR14UjvJ4pk33eNMMOxy2GIf9N+ZOsqTF7bO/ zluCutJY6h0k5EeJDBvdmPtawzTdKBJtZcsz/2dfNqya8npq1iJ+tbpmeC485/deB9vJ 9NsJpukkpyN3ceQfXJWBGLf6/7ot8kBYhIOlg= Received: by 10.231.158.132 with SMTP id f4mr5529405ibx.52.1277148045057; Mon, 21 Jun 2010 12:20:45 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-128-180.dsl.klmzmi.sbcglobal.net [99.181.128.180]) by mx.google.com with ESMTPS id r12sm23872600ibi.8.2010.06.21.12.20.43 (version=SSLv3 cipher=RC4-MD5); Mon, 21 Jun 2010 12:20:44 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C1FBB8A.6020907@dataix.net> Date: Mon, 21 Jun 2010 15:20:42 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100620 Thunderbird MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <20100617101541.GA90363@mech-cluster241.men.bris.ac.uk> <4C1A117A.9060608@dataix.net> <20100618085018.GA94427@mech-cluster241.men.bris.ac.uk> <4C1B63A1.3010604@dataix.net> <8639wgfnrk.fsf@ds4.des.no> <4C1F8444.80002@dataix.net> <86mxuofj40.fsf@ds4.des.no> <4C1F99E6.30202@dataix.net> <86aaqoffbg.fsf@ds4.des.no> In-Reply-To: <86aaqoffbg.fsf@ds4.des.no> X-Enigmail-Version: 1.0.1 OpenPGP: id=89D8547E Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org, Anton Shterenlikht , freebsd-ia64@freebsd.org Subject: Re: r209240 ia64 -> buildworld -> undefined reference to `lzma_physmem' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2010 19:20:46 -0000 On 06/21/2010 13:47, Dag-Erling Smørgrav wrote: > jhell writes: >> As to the point before you start pointing fingers as you are so gracious >> to do lately - The steps laid out are the steps I had once took to >> correct the similar problem. And I seem to be running on these systems >> fairly well mind you. > > They are still wrong, and they will not solve his problem. All they > will do is muddle the tracks and reduce our chances of ever finding out > what the problem really is. Actually I apologize as I originally read your fix to what I posted as cd to /usr/src/includes where as you are correct with those build options for a cd /usr/src. I do think that a full depends and includes build for the whole tree is a little expensive in this case but it would work the same either way. Though with what you said above (second paragraph) I would believe that trying to correct this problem first by finding out if the problem was laid out in the includes directory first would have been one step possibly in the right direction to solving the problem as I am just trying to recall what had actually solved that import of lzma issue. This is the thread with the discussion: http://bit.ly/dCuhHK Why on earth this is breaking on some machines and not on others is weird. Maybe a possibility of having the xz- port installed in comparison to the ones that don't... I didn't have that much time to analyze it when it came about. I can say that after he tried the build after the includes directory build that the `lzma_physmem' error he was getting in the subject line disappeared and he was left with just having to update libarchive & liblzma. > >> Praying for you, > > I'd rather you didn't. In reference to: http://bit.ly/dy4VSb ;) Regards, -- jhell