Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

If you get No such file error messages for files x509.h, ssl.h,
pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL
is not installed on your system. Either install OpenSSL first
or build with command: make slx SSLTYPE=none
`cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c
osdep.c:35:20: shadow.h: No such file or directory
In file included from osdep.c:46:
tz_sv4.c: In function `rfc822_timezone':
tz_sv4.c:30: error: `daylight' undeclared (first use in this function)
tz_sv4.c:30: error: (Each undeclared identifier is reported only once
tz_sv4.c:30: error: for each function it appears in.)
osdep.c: In function `checkpw':
osdep.c:113: warning: assignment makes pointer from integer without a cast
osdep.c:113: error: dereferencing pointer to incomplete type
osdep.c:114: error: dereferencing pointer to incomplete type
osdep.c:114: error: dereferencing pointer to incomplete type
osdep.c:115: error: dereferencing pointer to incomplete type
osdep.c:115: error: dereferencing pointer to incomplete type
osdep.c:116: error: dereferencing pointer to incomplete type
osdep.c:116: error: dereferencing pointer to incomplete type
osdep.c:117: error: dereferencing pointer to incomplete type
osdep.c:117: error: dereferencing pointer to incomplete type
osdep.c:117: error: dereferencing pointer to incomplete type
osdep.c:118: error: dereferencing pointer to incomplete type
osdep.c:118: error: dereferencing pointer to incomplete type
osdep.c:119: error: dereferencing pointer to incomplete type
osdep.c:119: error: dereferencing pointer to incomplete type
osdep.c:120: error: dereferencing pointer to incomplete type
osdep.c:120: error: dereferencing pointer to incomplete type
osdep.c:120: error: dereferencing pointer to incomplete type
osdep.c:127: error: dereferencing pointer to incomplete type
osdep.c:127: error: dereferencing pointer to incomplete type
make[3]: *** [osdep.o] Error 1
make[2]: *** [slx] Error 2
make[1]: *** [OSTYPE] Error 2
make: *** [slx] Error 2
+---------------------------------------------+
| Problems building c-client                  |
|                                             |
| Please check the output above for a         |
| possible explanation for this failure       |
+---------------------------------------------+


!!! ERROR: mail-client/pine-4.61-r2 failed.
!!! Function src_compile, Line 114, Exitcode 2
!!! compile problem
!!! If you need support, post the topmost build error, NOT this status message.

almost:/usr/portage/net-mail joe$ 

Reproducible: Always
Steps to Reproduce:

First time reporting on Gentoo on Mac OS X... here's my emerge info. This
occured when attempting to emerge pine on Mac OS X 10.3.8. 

Let me know if you need more info, want more testing, etc. Thanks guys!

almost:/usr/portage/net-mail joe$ emerge info
Password:
!!! Relying on the shell to locate gcc, this may break
!!! DISTCC, installing gcc-config and setting your current gcc
!!! profile will fix this
Portage 2.0.51-r15 (default-darwin/macos/10.3, gcc-3.3, libsystem-7.1-r0, 7.8.0
Power Macintosh)
=================================================================
System uname: 7.8.0 Power Macintosh powerpc
macos-20041118
Python:               [2.3 (#1, Sep 13 2003, 00:49:11)]
distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632)
[disabled]
dev-lang/python:     [Not Present]
sys-devel/autoconf:  [Not Present]
sys-devel/automake:  [Not Present]
sys-devel/binutils:  [Not Present]
sys-devel/libtool:   [Not Present]
virtual/os-headers:  7.1
ACCEPT_KEYWORDS="ppc-macos"
AUTOCLEAN="yes"
CFLAGS="-O2 -pipe"
CHOST="powerpc-apple-darwin"
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="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache collision-protect distlocks userpriv"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="ppc emboss ncurses nls ppc-macos readline"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY

Anything new with this one? Does latest 4.62-r2 work for you by any chance?

The problem appears identical when emerging pine-4.62-r2. The line numbers
match and the error message appears to be identical.

In order to ensure that pine builds right under os x, the following marked
lines should be added to the ebuild.  Pine already knows about OS X, so you
just need to tell it the correct platform.

        if use pam ; then
                target=lnp
        else
                target=slx
        fi

>        if use ppc-macos ; then
>                target=osx
>        fi

        ./build ${myconf} ${target} || die "compile problem"

Created an attachment (id=55182) [details]
Patch to make pine recognize that it is on os x

Okay, we have a few issues here. Firstly, pine does not build with either ldap,
pam or ssl.
The ldap problem is because pine expects libldap.a and we have the dylib
(dynamic) version. Is there
a real reason why pine needs the static version?

Secondly, pine installs pico, which is already provided by macos. Users of the
-collision-protect
profile may want to overwrite the Apple-provided pico, however I don't want to
block pine on 
collision-protect machines just because of pico. Should we rm pico if FEATURES
has collision-protect?

Thoughts on fixing either of those two issues would be appreciated. I am not a
pine user, so I am
going to rely on you guys to make sure things actually work as expected.

As for the pico issue, I think it's safe to rm pico from pine install and make
pine depend on already-installed pico (if you can find out how to reliably
check for its presence). Afaik pine doesn't even directly use pico, so it
shouldn't matter.

As for the dynlib vs. static issue, I suggest you contact upstream, namely
Eduardo Chappa (I'm not going to write his email here to protect him from spam,
it's easy to find anyway), who has helped me with some pine questions already
in the past.

On Tiger, pico is nothing more than a symlink:

% la /usr/bin/pico
lrwxr-xr-x   1 root  wheel  4 May 12 19:58 /usr/bin/pico -> nano

Emailed the maintainer about the library issue.

Still no new info about this issue?

Unfortunately, I was not able to get a response from the maintainer. If someone
can get a hold of him and 
ask about the static vs. dynmaic library issue that would be helpful.

Guys, j4rg0n is retired, and this bug has no activity for a year. Can someone
have a look at it please? Thanks!

heu.... Panther is not supported any more.  Sorry.  Just use mutt :p