From: Ivan Popivanov <popivan@gmx.net>
To: gdb@sources.redhat.com
Subject: Problems compiling GDB on AIX
Date: Sat, 28 May 2005 01:41:00 -0000 [thread overview]
Message-ID: <4297CC4B.4090301@gmx.net> (raw)
No problems compiling gdb-6.0, however, when I try to compile anything
newer I get from "make install" the error I pasted at the end of this
message. Note that I don't have root account and I compiled and
installed make, libtool and few other utilities under $HOME/installs.
I saw a thread saying that gdb-6.3 is broken on non GNU platforms
because gettext is not installed. My question is how can I install
gettext without being root? I mean I can compile and install it in
$HOME/installs, but how to make the headers and the libraries available
when GDB is building?
Thanks in advance!
Ivan
---------------------------------------------------------------------
make[2]: Leaving directory `/home/popivan/gdb-6.1.1/bfd/po'
make[2]: Entering directory `/home/popivan/gdb-6.1.1/bfd'
make[3]: Entering directory `/home/popivan/gdb-6.1.1/bfd'
make[3]: Nothing to be done for `install-exec-am'.
/bin/sh ./../mkinstalldirs /home/popivan/installs/lib
/bin/sh ./../mkinstalldirs /home/popivan/installs/include
/bin/sh ./libtool --mode=install ./install-sh -c libbfd.la
/home/popivan/installs/lib/libbfd.la
./install-sh -c .libs/libbfd.lai /home/popivan/installs/lib/libbfd.la
./libtool[4987]: ./install-sh: not found <<<< ./install-sh is
in the gdb directory ...
make[3]: *** [install_libbfd] Error 127
make[3]: Leaving directory `/home/popivan/gdb-6.1.1/bfd'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/popivan/gdb-6.1.1/bfd'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/popivan/gdb-6.1.1/bfd'
make: *** [install-bfd] Error 2
next reply other threads:[~2005-05-28 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 1:41 Ivan Popivanov [this message]
2005-05-28 2:17 ` Daniel Jacobowitz
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=4297CC4B.4090301@gmx.net \
--to=popivan@gmx.net \
--cc=gdb@sources.redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox