all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Fellinger <manveru@weez-int.com>
Subject: Re: Problems compiling on Archlinux 64
Date: Fri, 24 Nov 2006 11:32:29 +0900	[thread overview]
Message-ID: <200611241132.29293.manveru@weez-int.com> (raw)
In-Reply-To: <87fycbo52b.fsf@cyd.mit.edu>

On Thursday 23 November 2006 00:48, Chong Yidong wrote:
> Does this completely untested patch give good results (you'll have to
> regenerate configure to test it, of course)?

Alright, that did the trick!
Thank you _so_ much, i really hope this goes into the final release :)
If you have further things to try for me, just write, but this is definitly 
the path to success.

^manveru

>
> *** emacs/configure.in.~1.418.~	2006-11-14 10:54:05.000000000 -0500
> --- emacs/configure.in	2006-11-22 10:42:46.000000000 -0500
> ***************
> *** 1485,1490 ****
> --- 1485,1500 ----
>   AC_SYS_LARGEFILE
>
>
> + ### The standard library on x86-64 GNU/Linux distributions can
> + ### be located in either /usr/lib64 or /usr/lib.
> + case "${canonical}" in
> +   x86_64-*-linux-gnu* )
> +     if test -d /usr/lib64; then
> +       AC_DEFINE(HAVE_X86_64_LIB64_DIR, 1,
> +         [Define to 1 if the file /usr/lib64 exists.])
> + fi
> + esac
> +
>   dnl This function defintion taken from Gnome 2.0
>   dnl PKG_CHECK_MODULES(GSTUFF, gtk+-2.0 >= 1.3 glib = 1.3.4, action-if,
> action-not) dnl defines GSTUFF_LIBS, GSTUFF_CFLAGS, see pkg-config man page
> *** emacs/src/m/amdx86-64.h.~1.11.~	2006-10-30 09:06:42.000000000 -0500
> --- emacs/src/m/amdx86-64.h	2006-11-22 10:44:40.000000000 -0500
> ***************
> *** 128,134 ****
> --- 128,138 ----
>   #else /* !__OpenBSD__ && !__FreeBSD__ */
>
>   #undef START_FILES
> + #ifdef HAVE_X86_64_LIB64_DIR
>   #define START_FILES pre-crt0.o /usr/lib64/crt1.o /usr/lib64/crti.o
> + #else
> + #define START_FILES pre-crt0.o /usr/lib/crt1.o /usr/lib/crti.o
> + #endif
>
>   /* The duplicate -lgcc is intentional in the definition of LIB_STANDARD.
>      The reason is that some functions in libgcc.a call functions from
> libc.a, ***************
> *** 136,142 ****
> --- 140,150 ----
>      versions of ld are one-pass linkers, we need to mention -lgcc twice,
>      or else we risk getting unresolved externals.  */
>   #undef LIB_STANDARD
> + #ifdef HAVE_X86_64_LIB64_DIR
>   #define LIB_STANDARD -lgcc -lc -lgcc /usr/lib64/crtn.o
> + #else
> + #define LIB_STANDARD -lgcc -lc -lgcc /usr/lib/crtn.o
> + #endif
>
>   #endif /* __FreeBSD__ */

  parent reply	other threads:[~2006-11-24  2:32 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
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 [this message]
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=200611241132.29293.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 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.