View previous topic :: View next topic |
Author |
Message |
BennyP Guru
Joined: 09 May 2003 Posts: 503 Location: Jerusalem, Israel
|
Posted: Sat Oct 02, 2004 7:12 pm Post subject: dev-util/dialog-1.0.20040731 failed. |
|
|
Code: | gcc -mcpu=7450 -O2 -pipe -maltivec -mabi=altivec -mpowerpc-gfxopt -D_XOPEN_SOURCE=500 -D_POSIX_C_SOURCE -DHAVE_CONFIG_H -I. -I. -DLOCALEDIR=\"/usr/share/locale\" -c dialog.c
ar -cr libdialog.a rc.o calendar.o fselect.o timebox.o formbox.o guage.o tailbox.o arrows.o buttons.o checklist.o inputbox.o inputstr.o menubox.o mouse.o mousewget.o msgbox.o textbox.o ui_getc.o util.o version.o yesno.o
ranlib libdialog.a
*** Warning: inferring the mode of operation is deprecated.
*** Future versions of Libtool will require -mode=MODE be specified.
ranlib: warning: cannot infer operation mode from `libdialog.a'
ranlib: you must specify a MODE
Try `ranlib --help' for more information.
make: *** [libdialog.a] Error 1
make: *** Waiting for unfinished jobs.... |
i just sync'ed and emerged libtool before i did this _________________ Could it be? |
|
Back to top |
|
|
dubiboy n00b
Joined: 04 Aug 2003 Posts: 22 Location: Israel
|
Posted: Thu Jan 06, 2005 3:19 pm Post subject: dialog failing emerge |
|
|
I got a similar problem: on doing an
emerge dialog get:
Code: |
........
checking for initscr... no
checking for initscr in -lncursesw... no
checking for -lncursesw in /usr/local/lib... no
checking for -lncursesw in /usr/lib... no
configure: error: Cannot link ncursesw library
!!! ERROR: dev-util/dialog-1.0.20040731 failed.
!!! Function econf, Line 449, Exitcode 1
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.
|
Ideas anyone? |
|
Back to top |
|
|
Orpheus n00b
Joined: 30 Oct 2004 Posts: 6 Location: Melbourne, Australia
|
Posted: Sun Jan 09, 2005 1:48 am Post subject: |
|
|
The same problem occurs under Darwin 7.7 / Mac OS X 10.3.7 :
Code: |
>>> emerge (1 of 4) dev-util/dialog-1.0.20040731 to /
...
./configure --prefix=/usr --host=powerpc-apple-darwin --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-ncursesw
...
checking for initscr... no
checking for initscr in -lncursesw... no
checking for -lncursesw in /usr/lib... no
configure: error: Cannot link ncursesw library
|
even though ncurses is installed, lives in /usr/lib, and exports such a function:
Code: |
> ls -l /usr/lib/libncurses*
-rw-r--r-- 1 root wheel 279000 27 Dec 00:35 /usr/lib/libncurses.5.dylib
lrwxr-xr-x 1 root wheel 18 26 Dec 18:33 /usr/lib/libncurses.dylib -> libncurses.5.dylib
> cat /usr/include/ncurses.h | grep "initscr"
extern NCURSES_EXPORT(WINDOW *) initscr (void); /* implemented */
|
Though somewhat curiously, attempting to install the ncurses package from portage as suggested in another thread not only fails to solve the problem, but indeed, fails to attempt doing anything at all:
Code: |
>>> Install ncurses-8.1 into /var/tmp/portage/ncurses-8.1/image/ category sys-libs
man:
prepallstrip:
strip:
>>> Completed installing into /var/tmp/portage/ncurses-8.1/image/
* checking 0 files for package collision
|
Any ideas?
The obligatory emerge info:
Code: |
Portage 2.0.51-r3 (default-macos-10.3, gcc-3.3, libsystem-7.1-r0, 7.7.0 Power Macintosh)
=================================================================
System uname: 7.7.0 Power Macintosh powerpc
macos-20041118
distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632) [disabled]
Autoconf:
Automake:
Binutils:
Headers:
Libtools:
ACCEPT_KEYWORDS="ppc-macos ~ppc-macos"
AUTOCLEAN="yes"
CFLAGS="-mcpu=G4 -mabi=altivec -maltivec -O2 -pipe"
CHOST="powerpc-apple-darwin"
COMPILER=""
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-mcpu=G4 -mabi=altivec -maltivec -O2 -pipe"
DISTDIR="/usr/local/portage/source"
FEATURES="autoaddcvs ccache collision-protect distlocks"
GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/local/portage/packages/ppc-macos"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/local/portage/current"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="macos altivec emacs gif imap jpeg mbox mime motif plotutils png posix samba spell ssl tetex tiff truetype unicode"
|
|
|
Back to top |
|
|
Orpheus n00b
Joined: 30 Oct 2004 Posts: 6 Location: Melbourne, Australia
|
Posted: Sun Jan 09, 2005 2:22 am Post subject: |
|
|
As a temporary solution to the problem, I have hacked the ebuild :
Code: |
src_compile() {
export LANG=C
use unicode && ncursesw="" # was "ncursesw=w" changed to resolve link error
econf "--with-ncurses${ncursesw}" || die "configure failed"
emake || die "build failed"
}
|
which allows it to link properly against the version of nucurses installed under Mac OS X (and possibly under linux as well by the looks of the above posts). |
|
Back to top |
|
|
fonzarely n00b
Joined: 02 Sep 2003 Posts: 38 Location: Paris
|
Posted: Thu Jan 13, 2005 12:40 am Post subject: |
|
|
USE=-unicode emerge dialog |
|
Back to top |
|
|
dubiboy n00b
Joined: 04 Aug 2003 Posts: 22 Location: Israel
|
Posted: Thu Jan 13, 2005 2:11 pm Post subject: |
|
|
Thanks fonzarely,
That does the trick |
|
Back to top |
|
|
robet l33t
Joined: 06 Sep 2004 Posts: 807 Location: Earth/NorthAmerica/USA/NY
|
|
Back to top |
|
|
duderonomy Guru
Joined: 20 Mar 2004 Posts: 349 Location: SF Bay Area
|
Posted: Thu Jun 02, 2005 6:35 am Post subject: |
|
|
merely to be pedantic...
is it not the /etc/portage/package.use file,
that your sugggestion will work as suggested ?
Cheers,
D |
|
Back to top |
|
|
mel_82 Tux's lil' helper
Joined: 25 Oct 2004 Posts: 117 Location: Somewhere in Italy
|
Posted: Mon Oct 24, 2005 1:04 am Post subject: |
|
|
I think
Code: | USE="unicode" emerge --newuse ncurses dialog |
will be a better solution.
It will fix the ncurses unicode support, i guess. |
|
Back to top |
|
|
dmartinsca Guru
Joined: 09 Dec 2005 Posts: 303 Location: Ontario, Canada
|
Posted: Sat Dec 24, 2005 12:49 am Post subject: |
|
|
mel_82 wrote: | I think
Code: | USE="unicode" emerge --newuse ncurses dialog |
will be a better solution.
It will fix the ncurses unicode support, i guess. |
Yes, seems the ncurses library from the install was compiled w/o unicode so it needs to be recompiled |
|
Back to top |
|
|
nick843 n00b
Joined: 01 Nov 2005 Posts: 25
|
Posted: Fri Jan 20, 2006 2:55 am Post subject: |
|
|
If "emerge --nweuse ncurses dialog" fixes this for everyone involved, [SOLVED] should be added to the thread subject. It worked for me! |
|
Back to top |
|
|
k_klunz n00b
Joined: 03 Dec 2004 Posts: 36 Location: Kaiserslautern, Rheinland-Pfalz, Germany, Europe
|
Posted: Wed Mar 15, 2006 11:25 am Post subject: |
|
|
Just wanted to add, the postet solution worked for me too, so a [SOLVED] would be appropriate
greetz
Klunz |
|
Back to top |
|
|
|