From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 86C60138461 for ; Sun, 13 Jan 2013 19:46:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 564C721C0E3; Sun, 13 Jan 2013 19:46:20 +0000 (UTC) Received: from nm14.access.bullet.mail.sp2.yahoo.com (nm14.access.bullet.mail.sp2.yahoo.com [98.139.44.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7944A21C0CC for ; Sun, 13 Jan 2013 19:46:18 +0000 (UTC) Received: from [98.139.44.105] by nm14.access.bullet.mail.sp2.yahoo.com with NNFMP; 13 Jan 2013 19:46:17 -0000 Received: from [67.195.14.95] by tm10.access.bullet.mail.sp2.yahoo.com with NNFMP; 13 Jan 2013 19:46:17 -0000 Received: from [127.0.0.1] by smtp110.sbc.mail.gq1.yahoo.com with NNFMP; 13 Jan 2013 19:46:17 -0000 X-Yahoo-Newman-Id: 228476.46109.bm@smtp110.sbc.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: GA08q0AVM1lCNke5vkoqS6rlishnG_ePKMlbCkh6ck1TkAG anPx7blpdmIbm93Q_icQ8kxH9Ns06G_H.DwTGvt0cguS4lQlgqs499p2NsLJ tRMpbTYOtg.bR1KZ2_cVlgvscPM1nQ3OUB3X9Lsf1em9e9NVwTgmHFeqUouW 1iiA9Qfg0rfbELITe.K3Z3e5O31U3qJ95V5LHBd_Rr9IUobTebai2P94zaOm yKxu7e3xE01MDFPzvb07zFaHV517i40VXhK.opTpKEJWHUdAE5kamA5hXf.G TF.KknZhe.JFPxhs5sdP.LE5Nhh6DV83n4VBr04Zm1adOhvq8.c1VJ8NEonJ aQkKeMmJ9nbjV3IN4.mV2dfJy8vesNIW7OJ1dZsfYSF07CZuwqHa2u4t51NU MRxzn51DOdB6Uu7YzkbkINaER4bdSYmKG_RLreHTaQRUzmBGn5nRbhYORkJm UQ80q4j7vLMuSGOVFW8zmdwjg_.EjOYVZ.LCpw6m58Jyl12WTwnHg75kVxSa VS21thGteow2wUJb0uaNsFtVJ_Vcps5Pr3Q-- X-Yahoo-SMTP: oM3WcDSswBC7zv73TQKEsi7eAZ0- Received: from [192.168.1.2] (w41ter@69.234.183.226 with plain) by smtp110.sbc.mail.gq1.yahoo.com with SMTP; 13 Jan 2013 11:46:17 -0800 PST Message-ID: <50F30F15.80108@gmail.com> Date: Sun, 13 Jan 2013 11:46:29 -0800 From: walt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20121128 Thunderbird/18.0 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 To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: Ekopath compiler failing to build - something about glibc development files References: <50F259F7.9050108@wht.com.au> In-Reply-To: <50F259F7.9050108@wht.com.au> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 75541a2c-8e82-464c-b662-dd399c2e815a X-Archives-Hash: 0c811982fb26b6b297955e503ca05fc2 On 01/12/2013 10:53 PM, Andrew Lowe wrote: > Hi all, > I've got the ekopath compiler installed on my machine and Portage wants to update it, but fails. Before I go to the trouble of filling out a full bug report, does anyone have any ideas as to the problem? I think it is in the 5th line, "Configuration failed..." > > ************************ > >>>> Install ekopath-4.0.12.1_pre20121102 into /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image/ category dev-lang > Problem running post-install step. Installation may not complete correctly > Configuration failed. Make sure you have glibc developement files installed. > Additional information: > ==== > In file included from /usr/include/endian.h:61, > from /usr/include/pthread.h:23, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_mutex-pthread.h:52, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_mutex.h:71, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_strref.h:41, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/string:44, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/loc/_locale.h:37, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/rw/_iosbase.h:37, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/streambuf:40, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/ostream:45, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/istream:44, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/include/4.0.12.1/stl/iostream:34, > from /var/tmp/portage/dev-lang/ekopath-4.0.12.1_pre20121102/image//opt/ekopath/test.cpp:3: > /usr/include/bits/byteswap.h: In function 'unsigned int __bswap_32(unsigned int)': > /usr/include/bits/byteswap.h:46: error: '__builtin_bswap32' was not declared in this scope > /usr/include/bits/byteswap.h: In function 'long long unsigned int __bswap_64(long long unsigned int)': > /usr/include/bits/byteswap.h:110: error: '__builtin_bswap64' was not declared in this scope > > ***************************** > > From all of the above, I think the important part is that I need to install some "glibc developement files". A google search doesn't point me in the direction of what these might be. According to "eix glibc", I have debug turned OFF - is this the problem? Or is this for debugging glibc and not my code? I think if I can work out the development files stuff, the bswap64 problem will fix itself. That's obviously a bug in the ebuild because you should never need to install dependencies on your own -- that's a big part of what the ebuild is supposed to do. Because gentoo compiles most packages from source, all of the development files are included with the main package (including glibc) unlike most linux distros that do package them separately because many linux users are not going to compile anything. It's true that the gentoo glibc package might have omitted some of the headers by mistake, but I don't think so in this case because I just wrote, compiled, and ran a C program that includes byteswap.h and got no errors. The bottom line is that the ekopath package is broken -- for reasons I don't know, but the package maintainer should ;)