From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 15086@debbugs.gnu.org
Subject: bug#15086: 24.3.50; NS variant does not build on PPC Tiger because of missing qualifier before 'vector'
Date: Tue, 13 Aug 2013 20:22:14 +0200 [thread overview]
Message-ID: <96FAC662-38C4-4C22-B6C5-508AB797807D@Freenet.DE> (raw)
In-Reply-To: <10A7FA47-1BE7-430A-A5CC-09DB5626B595@swipnet.se>
Am 13.08.2013 um 17:47 schrieb Jan Djärv:
> I've checked in an attemted fix. I can't check it as 10.4 is
> really old and I don't have any around.
Your fix does fix the problem in nsterm.m, but here is another error
(+ warnings), when temacs is being built:
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple
definitions of symbol _BC
terminfo.o definition of _BC in section (__DATA,__common)
/opt/local/lib/libncurses.dylib(single module) definition of _BC
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple
definitions of symbol _PC
terminfo.o definition of _PC in section (__DATA,__common)
/opt/local/lib/libncurses.dylib(single module) definition of _PC
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning multiple
definitions of symbol _UP
terminfo.o definition of _UP in section (__DATA,__common)
/opt/local/lib/libncurses.dylib(single module) definition of _UP
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
_ns_check_menu_open
_ns_check_pending_open_menu
--
Greetings
Pete
Don't just do something, sit there.
next prev parent reply other threads:[~2013-08-13 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 11:17 bug#15086: 24.3.50; NS variant does not build on PPC Tiger because of missing qualifier before 'vector' Peter Dyballa
2013-08-13 15:47 ` Jan Djärv
2013-08-13 16:46 ` Peter Dyballa
2013-08-13 18:22 ` Peter Dyballa [this message]
2013-08-13 20:25 ` Jan Djärv
2013-08-13 22:22 ` Peter Dyballa
2013-08-14 10:18 ` Peter Dyballa
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=96FAC662-38C4-4C22-B6C5-508AB797807D@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=15086@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
/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.