unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Fellinger <manveru@weez-int.com>
Subject: Re: Problems compiling on Archlinux 64
Date: Wed, 22 Nov 2006 10:29:57 +0900	[thread overview]
Message-ID: <200611221029.57786.manveru@weez-int.com> (raw)
In-Reply-To: <874psswt1o.fsf@cyd.mit.edu>

On Wednesday 22 November 2006 03:31, Chong Yidong wrote:
> Michael Fellinger <manveru@weez-int.com> writes:
> > make[2]: *** No rule to make target `/usr/lib64/crt1.o', needed by
> > `temacs'. Stop.
> > make[2]: Leaving directory
> > `/home/manveru/pkgbuilds/emacs-cvs/src/emacs/src' make[1]: ***
> > [bootstrap-build] Error 2
> > make[1]: Leaving directory `/home/manveru/pkgbuilds/emacs-cvs/src/emacs'
> > make: *** [bootstrap] Error 2
> >
> > I was told that this directory (/usr/lib64) does not exist since
> > Archlinux follows the LFS and Archlinux64 the CLFS standards. The same
> > seems to be the case for FreeBSD.
>
> Do other amdx86-64 distributions use /usr/lib64?  If so, how do we
> distinguish between the two cases?

Well, the simplest way i could come up with is to look if such a folder exists 
at all simply doing this check after looking up `arch` returns a 
64bit-system.
As far as i know quite some distributions use /usr/lib64 to use both 64bit and 
32bit (in /usr/lib) libraries. However, distributions who do not support 
32bit libs at all only use /usr/lib
this is the case (only as far as i know) for FreeBSD (sorry guys, of course 
it's _no_ distribution ;), LFS (by default), Slackware (Slax), Archlinux and 
Gentoo.
Some more might be out there, especially all that are based on the distros i 
mentioned.

thanks again for looking into this.

^manveru

  reply	other threads:[~2006-11-22  1:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 11:55 Problems compiling on Archlinux 64 Michael Fellinger
2006-11-21 18:31 ` Chong Yidong
2006-11-22  1:29   ` Michael Fellinger [this message]
2006-11-22 11:53     ` Giorgos Keramidas
2006-11-24  1:27       ` Michael Fellinger
2006-11-25  5:06         ` Nick Roberts
2006-11-25  5:46           ` Alfred M. Szmidt
2006-11-26 21:29             ` Chong Yidong
2006-11-26 21:40               ` Alfred M. Szmidt
2006-11-27  4:11                 ` Giorgos Keramidas
2006-11-25  6:59         ` Richard Stallman
2006-11-22 15:48     ` Chong Yidong
2006-11-23 15:12       ` Giorgos Keramidas
2006-11-24  2:32       ` Michael Fellinger
2006-11-28  0:34       ` Glenn Morris
2006-11-28  0:49         ` Glenn Morris
2006-11-28  0:58         ` Chong Yidong
2006-11-28  1:05           ` Glenn Morris
2006-11-28 16:04             ` Chong Yidong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611221029.57786.manveru@weez-int.com \
    --to=manveru@weez-int.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).