From: Martin Schlemmer <azarah@gentoo.org>
To: kumba@gentoo.tamperd.net
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>, gcc-porting@gentoo.org
Subject: Re: [gentoo-dev] Bleeding Edge Package Compile Failures
Date: 28 Jul 2003 21:06:38 +0200 [thread overview]
Message-ID: <1059419195.8206.82.camel@nosferatu.lan> (raw)
In-Reply-To: <3F247D8B.4060209@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
On Mon, 2003-07-28 at 03:34, Kumba wrote:
> //--------------------------
> =sys-libs/pam-0.75-r11
>
Works fine here - check your C[XX]FLAGS.
> //--------------------------
> =net-libs/liblockfile-1.03
>
Fixed in -r1.
> //--------------------------
> =sys-apps/modutils-2.4.25
> =sys-apps/module-init-tools-0.9.12-r1
>
Same issue, ill look into it.
> //--------------------------
> =sys-apps/parted-1.6.5
>
> Notes: Using sys-apps/parted-1.6.5-r1, this problem does not occur.
> However, -r1 of parted is not yet marked stable or even unstable on x86.
>
Mark it unstable (or stable if -r0 is such).
> //--------------------------
> =net-analyzer/tcpdump-3.7.2
>
Seems like an issue with the gcc in question's macro parser. I
will look into this.
>
> So anyone got any ideas on all this? That's not half bad for ~207
> packages. Some of these I don't think are gcc-3.3 issues, but one never
> knows (like the pam issue).
>
Cheers,
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-28 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 1:34 [gentoo-dev] Bleeding Edge Package Compile Failures Kumba
2003-07-28 19:06 ` Martin Schlemmer [this message]
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=1059419195.8206.82.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gcc-porting@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=kumba@gentoo.tamperd.net \
/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