unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cyrus Harmon <ch-emacs@bobobeach.com>
To: William Xu <william.xwl@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: trunk build failure on Solaris 2.6
Date: Fri, 19 Oct 2007 00:10:07 -0700	[thread overview]
Message-ID: <4C8DA280-30A2-4DA1-BD07-DF54C022E5FF@bobobeach.com> (raw)
In-Reply-To: <m2ejfrg3t9.fsf@gmail.com>

FWIW, I see the same error building on MacOS X 10.4.10

Cyrus

On Oct 18, 2007, at 8:51 PM, William Xu wrote:

> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> Does compilation complete with this patch applied?
>
> Still same error here:
>
> gcc  -prebind -framework Carbon -framework QuickTime -Xlinker - 
> headerpad
> -Xlinker 690  -o temacs pre-crt0.o dispnew.o frame.o scroll.o xdisp.o
> window.o charset.o coding.o category.o ccl.o cm.o term.o terminal.o
> xfaces.o   emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o
> filelock.o insdel.o marker.o minibuf.o fileio.o dired.o filemode.o
> cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o
> data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o print.o  
> lread.o
> abbrev.o syntax.o unexmacosx.o bytecode.o process.o callproc.o
> region-cache.o sound.o atimer.o doprnt.o strftime.o intervals.o
> textprop.o composite.o md5.o  mac.o macterm.o macfns.o macmenu.o
> macselect.o fontset.o fringe.o image.o  terminfo.o lastfile.o
> -lncurses
> /usr/bin/ld: warning prebinding disabled because of undefined symbols
> /usr/bin/ld: Undefined symbols:
> _res_9_init
> collect2: ld returned 1 exit status
> make[2]: *** [temacs] Error 1
> make[1]: *** [bootstrap-build] Error 2
> make: *** [bootstrap] Error 2
>
> -- 
> William
>
> http://williamxu.net9.org
>
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel

  parent reply	other threads:[~2007-10-19  7:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  0:45 trunk build failure on Solaris 2.6 Katsumi Yamaoka
2007-10-19  2:50 ` William Xu
2007-10-19  3:12 ` Chong Yidong
2007-10-19  3:51   ` William Xu
2007-10-19  4:22     ` Chong Yidong
2007-10-19  5:47       ` William Xu
2007-10-19 15:29         ` Chong Yidong
2007-10-19 16:20           ` William Xu
2007-10-19 19:48       ` Chong Yidong
2007-10-19 20:31         ` Dan Nicolaescu
2007-10-19 20:42           ` Chong Yidong
2007-10-20  1:42             ` YAMAMOTO Mitsuharu
2007-10-20 17:05               ` Chong Yidong
2007-10-21  5:10                 ` YAMAMOTO Mitsuharu
2007-10-21  5:46                   ` William Xu
2007-10-22 14:46                   ` Chong Yidong
2007-11-05 11:12                     ` Mark Aufflick
2007-11-06  2:15                       ` Richard Stallman
2007-10-21  2:22             ` William Xu
2007-10-20  0:31           ` Evil Boris
2007-10-19  7:10     ` Cyrus Harmon [this message]
2007-10-19  4:33   ` Katsumi Yamaoka

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=4C8DA280-30A2-4DA1-BD07-DF54C022E5FF@bobobeach.com \
    --to=ch-emacs@bobobeach.com \
    --cc=emacs-devel@gnu.org \
    --cc=william.xwl@gmail.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).