all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Fellinger <manveru@weez-int.com>
Cc: ams@gnu.org
Subject: Problems compiling on Archlinux 64
Date: Tue, 21 Nov 2006 20:55:00 +0900	[thread overview]
Message-ID: <200611212055.01073.manveru@weez-int.com> (raw)

Hello List,

This is my first mail to this list and i just started out with emacs... hope i 
don't break any rules here ;)

However, since we just have the emacs22 pretest period, i thought i should 
give it a try and went to build it on an archlinux 64bit system.

result: surprise, surprise, it won't build.
reason: there is no /usr/lib64 directory
backtrace:
make[2]: Leaving directory `/home/manveru/pkgbuilds/emacs-cvs/src/emacs/lisp'
(cd src; make -w bootstrap)
make[2]: Entering directory `/home/manveru/pkgbuilds/emacs-cvs/src/emacs/src'
gcc -c -D_BSD_SOURCE   -Demacs -DHAVE_CONFIG_H -DUSE_LUCID  -I. -I/home/manveru/pkgbuilds/emacs-cvs/src/emacs/src -D_BSD_SOURCE -I/usr/include/alsa -g -O2 -Wno-pointer-sign  
pre-crt0.c
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.

From m/amsx86-64.h:
> The libraries for binaries native to the build host's architecture are 
installed under /usr/lib in FreeBSD, and the ones that need special paths are 
32-bit compatibility libraries (installed under /usr/lib32).  To build a 
native binary of Emacs on FreeBSD/amd64 we can just point to /usr/lib.
And because of that, emacs fails to compile since it cannot 
find /usr/lib64/(crt1.o|crti.o)

I have no proposed solution apart from providing a different header with 
different paths, but i guess you guys know how to figure that out (my C-fu is 
rather weak)

Thanks for your help in advance.
^manveru


my System:
[manveru@sigma emacs]$ uname -a
Linux sigma 2.6.18-ARCH #1 SMP PREEMPT Tue Oct 3 21:59:13 IST 2006 x86_64 AMD 
Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux

the crt1.o:
[manveru@sigma emacs]$ file /usr/lib/crt1.o
/usr/lib/crt1.o: ELF 64-bit LSB relocatable, AMD x86-64, version 1 (SYSV), for 
GNU/Linux 2.6.6, not stripped

             reply	other threads:[~2006-11-21 11:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 11:55 Michael Fellinger [this message]
2006-11-21 18:31 ` Problems compiling on Archlinux 64 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
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

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

  git send-email \
    --in-reply-to=200611212055.01073.manveru@weez-int.com \
    --to=manveru@weez-int.com \
    --cc=ams@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.