From: Stefan Jones <stefan.jones@multigig.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] PAM appears B0rked
Date: 21 Oct 2002 17:10:08 +0100 [thread overview]
Message-ID: <1035216612.30239.14.camel@sajX.multigig> (raw)
In-Reply-To: <61170000.1035214489@phaedrus.syroidmanor.com>
Recompile glib, hit this problem myself
Stefan
On Mon, 2002-10-21 at 16:34, Tom Syroid wrote:
> Devs,
>
> I did the ACCEPT_KEYWORDS="~x86" this morning and proceeded to emerge the
> long list of updates available. But what appears to be a lib error in PAM
> (sorry, not a programmer) is holding up the works. Is this just me, or has
> anyone else experienced the same?
>
> Best,
> /tom
>
> ---snip---
> config.y: In function `_pc_yyparse':
> config.y:103: warning: char format, void arg (arg 4)
> /usr/share/bison/bison.simple:799: warning: passing arg 1 of `_pc_yyerror'
> discards qualifi
> /usr/share/bison/bison.simple:924: warning: passing arg 1 of `_pc_yyerror'
> discards qualifi
> /usr/lib/libglib.a(gstrfuncs.o)(.text+0x734): In function `g_strdown':
> : undefined reference to `__ctype_tolower'
> /usr/lib/libglib.a(gstrfuncs.o)(.text+0x7b4): In function `g_strup':
> : undefined reference to `__ctype_toupper'
> /usr/lib/libglib.a(gstrfuncs.o)(.text+0x10da): In function `g_strchug':
> : undefined reference to `__ctype_b'
> /usr/lib/libglib.a(gstrfuncs.o)(.text+0x119c): In function `g_strchomp':
> : undefined reference to `__ctype_b'
> /usr/lib/libglib.a(gstrfuncs.o)(.text+0x11bc): In function `g_strchomp':
> : undefined reference to `__ctype_b'
> /usr/lib/libglib.a(gstring.o)(.text+0x584): In function `g_string_down':
> : undefined reference to `__ctype_tolower'
> /usr/lib/libglib.a(gstring.o)(.text+0x604): In function `g_string_up':
> : undefined reference to `__ctype_toupper'
> collect2: ld returned 1 exit status
> make[2]: *** [pam_console_apply] Error 1
> make[2]: Leaving directory
> `/var/tmp/portage/pam-0.75-r8/work/Linux-PAM-0.75/modules/pam_co
> make[1]: *** [all] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/pam-0.75-r8/work/Linux-PAM-0.75/modules'
> make: *** [modules] Error 2
>
> !!! ERROR: The ebuild did not complete successfully.
> !!! Function src_compile, Line 101, Exitcode 2
> !!! Failed to build
> ---ends---
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-10-21 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 15:34 [gentoo-dev] PAM appears B0rked Tom Syroid
2002-10-21 16:10 ` Stefan Jones [this message]
2002-10-21 20:37 ` Matthew J. Turk
2002-10-21 21:49 ` Spider
2002-10-21 22:12 ` Alan
2002-10-21 22:15 ` [gentoo-dev] PAM appears B0rked RESOLVED Tom Syroid
2002-10-21 22:22 ` Marc Chabrol
2002-10-21 22:43 ` Tom Syroid
2002-10-21 23:15 ` [gentoo-dev] OpenSSH/libwrap error RESOLVED Tom Syroid
2002-10-21 23:27 ` Marc Chabrol
2002-10-26 0:30 ` [gentoo-dev] PAM appears B0rked RESOLVED Martin Schlemmer
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=1035216612.30239.14.camel@sajX.multigig \
--to=stefan.jones@multigig.com \
--cc=gentoo-dev@gentoo.org \
/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