From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266658AbUFWUf3 (ORCPT ); Wed, 23 Jun 2004 16:35:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266659AbUFWUf3 (ORCPT ); Wed, 23 Jun 2004 16:35:29 -0400 Received: from galaxy.lunarpages.com ([64.235.234.165]:55268 "EHLO galaxy.lunarpages.com") by vger.kernel.org with ESMTP id S266658AbUFWUfZ (ORCPT ); Wed, 23 Jun 2004 16:35:25 -0400 Message-ID: <40D9E98C.5030804@rooseveltmedia.com> Date: Wed, 23 Jun 2004 16:35:24 -0400 From: Cyrus Adkisson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.6) Gecko/20040510 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linux Kernel Subject: what is up with lib64? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - galaxy.lunarpages.com X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - rooseveltmedia.com X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Can someone explain to me why x86_64 has lib64 directories and how lib64 is supposed to work with the lib directories that are already there? I'm having a very difficult time getting anything to compile from source. FC2, dual x86_64 Cyrus