This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Debian/SPARC: /usr/lib64 vs. /usr/lib/64

From: "David S. Miller" <davem at redhat dot com>
To: jakub at redhat dot com
Cc: fw at deneb dot enyo dot de, gcc at gcc dot gnu dot org
Date: Wed, 01 May 2002 23:03:57 -0700 (PDT)
Subject: Re: Debian/SPARC: /usr/lib64 vs. /usr/lib/64
References: <87pu0fporo.fsf@deneb.enyo.de><20020502074425.H32482@sunsite.ms.mff.cuni.cz>

   From: Jakub Jelinek <jakub@redhat.com>
   Date: Thu, 2 May 2002 07:44:25 +0200

   On Wed, May 01, 2002 at 11:00:11PM +0200, Florian Weimer wrote:
   > What's the correct approach here?

   IMHO Debian should just read LSB/FHS and do what everybody else is doing
   (not only for SPARC, but x86_64, AFAIK ppc64, s390x, etc.).

I agree with Jakub.

Out of curiosity I walked around the www.linuxbase.org website and I
don't see any specifications for these issues.  Does anyone know where
they might be hiding? :-)

Follow-Ups:
- Re: Debian/SPARC: /usr/lib64 vs. /usr/lib/64
  - From: Jakub Jelinek

References:
- Debian/SPARC: /usr/lib64 vs. /usr/lib/64
  - From: Florian Weimer
- Re: Debian/SPARC: /usr/lib64 vs. /usr/lib/64
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]