From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QUL2S-0001NW-5q for garchives@archives.gentoo.org; Wed, 08 Jun 2011 15:51:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E4C841C08A; Wed, 8 Jun 2011 15:49:04 +0000 (UTC) Received: from mail-vx0-f181.google.com (mail-vx0-f181.google.com [209.85.220.181]) by pigeon.gentoo.org (Postfix) with ESMTP id B25A11C08A for ; Wed, 8 Jun 2011 15:49:04 +0000 (UTC) Received: by vxb39 with SMTP id 39so563631vxb.40 for ; Wed, 08 Jun 2011 08:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:content-type; bh=fWnKcnsNr3z1mJxZkiXRmFlIuknYtUnZnChkFNS5rK8=; b=wBhtOgUgzmrn5sec0EHz+nZjyEa3AtjEe5eaXRVb8btkhbOiX58nKXSAbYBFc5M6kv L1/10jkNmBcHWahIR7+9ZxLVQnoNl2V49GOLMNAhcH3mGQ3+c/AUVkM9Y+/7wng0ktPF tVxx/5Rh8QJRCPExHvyvBXuG6HX5XiZgpEVrg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=uP5/JoJ9qe9Q9VkimfqyJ3EH53xB7zMw4FcSaEEhwMYkG7T0eb1a57wbQOOJ6h/buI b9vSECkH4jdONW1TPPY7AeKAnmTiFH4fhCIq65c56OJu9iM+RHTvJpf1HjGrC4Q4eS1V W8SLf+z5S4MNaxZ9B6EH+UnMR62Gh+eeiCMfk= Received: by 10.52.18.14 with SMTP id s14mr1171459vdd.164.1307548144122; Wed, 08 Jun 2011 08:49:04 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Sender: paul.hartman@gmail.com Received: by 10.52.169.8 with HTTP; Wed, 8 Jun 2011 08:48:44 -0700 (PDT) In-Reply-To: <87mxhsiygz.fsf@eps142.cdf.udc.es> References: <874o4g3yas.fsf@eps142.cdf.udc.es> <87aae4hcqg.fsf@eps142.cdf.udc.es> <87mxhsiygz.fsf@eps142.cdf.udc.es> From: Paul Hartman Date: Wed, 8 Jun 2011 10:48:44 -0500 X-Google-Sender-Auth: qHcNcnDdb9VN0Vx6kCYBgWWzTJ8 Message-ID: Subject: Re: [gentoo-user] Re: ebuild not inserting soname, therefore emerging zlib fails To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: X-Archives-Hash: 178c5e9888e435bcc7bd3fc9562be232 On Wed, Jun 8, 2011 at 2:17 AM, Alberto Luaces wrote: > Alberto Luaces writes: > >> Hi Paul, >> >> Paul Hartman writes: >> >>> On Fri, May 27, 2011 at 11:26 AM, Alberto Luaces wrote: >>>> Hello, >>>> >>>> I have searched quite a bit for an error I'm having when emerging >>>> current zlib-1.2.5-r2. The problem is that somehow the soname is not >>>> written in the .so file, and the build process fails. I attach all the >>>> build logs in case I have some obvious misconfiguration that I should be >>>> aware of. I have not changed my CHOSTS or things like that. >>>> >>>> I recompiled the previous version and happened the same, but it seems >>>> at that time not having a soname was not forbidden by the ebuild and I >>>> got just a QA notice. >>>> >>>> If I try to compile zlib from the /var/tmp/portage... directory the >>>> library compiles fine and, in addition, the soname is included this >>>> time. I tried to trace the eclasses in order to know what was happening >>>> but I couldn't. >>> >>> Hi, >>> >>> Based on your settings I am guessing you have used distcc in the past, >>> even though you have disabled it now. >> >> You are right, well spotted! >> >>> I think zlib's configure makes some changes based on if it thinks you >>> use distcc or not. I would try to unset CC in environment and remove >>> -m32 from your CFLAGS and see if it is any different. It's only a >>> guess and you can change it back if it doesn't work. >>> >> >> My environment CC was empty or already unset, I removed the `-m32' tag >> but it happens the same. >> >>> >>> I would also select again your preferences in gcc-config and >>> binutils-config, run env-update and source /etc/profile just to be >>> sure everything is in working order. :) >>> >> >> I followed your advice. I have only another compiler, the mingw cross >> compiler, but I checked that is not selected byb default. >> >> Nevertheless, thank you for your help. You gave me the idea on focusing >> on zlib's configure script in order to see what is failing in the >> detection process. > > I finally found it. Turns out that for using distcc I had to set CC=cc > in make.conf, and with that setting, zlib's configure avoided to build > the shared library. Unsetting CC in make.conf made it working again. Glad to hear it, I knew something about that CC looked suspicious. :)