From: "Alfred M. Szmidt" <ams@gnu.org>
Cc: manveru@weez-int.com, emacs-devel@gnu.org
Subject: Re: Problems compiling on Archlinux 64
Date: Sat, 25 Nov 2006 06:46:35 +0100 (CET) [thread overview]
Message-ID: <20061125054635.7481344030@Psilocybe.Update.UU.SE> (raw)
In-Reply-To: <17767.53066.391735.78334@kahikatea.snap.net.nz> (message from Nick Roberts on Sat, 25 Nov 2006 18:06:18 +1300)
I think this would be a case of the tail wagging the dog. There
are over 100 GNU/Linux distributions and I don't think Emacs should
have to test for each of them. Aren't there some standards that
the distributions conform to?
No, sadly. Host libraries are supposed to be put in /usr/lib, and not
/usr/lib64 if the host is 64-bit, so the best/simplest solution is
probably to not use /usr/lib64 at all, and mention in etc/PROBLEMS
that on 64-bit GNU/Linux systems that install 64-bit libraries in
/usr/lib64 (and 32-bit in /usr/lib) that one has to modify
m/amdx86-64.h or something along those lines.
Another way might be to use the output of `gcc -print-search-dirs',
and check in which directory crti.o exists in.
My two groszy.
next prev parent reply other threads:[~2006-11-25 5:46 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
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 [this message]
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=20061125054635.7481344030@Psilocybe.Update.UU.SE \
--to=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=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).