From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] что делать с h2ph (perl-1:5.8.8-alt4: rebuild failed)
Date: Mon, 9 Oct 2006 00:02:38 +0400
Message-ID: <20061008200238.GA13391@basalt.office.altlinux.org> (raw)
In-Reply-To: <20061008194323.GA23308@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Sun, Oct 08, 2006 at 11:43:24PM +0400, Alexey Tourbin wrote:
> On Wed, Oct 04, 2006 at 10:11:57PM +0400, QA Team Robot wrote:
> > syntax error at /usr/src/tmp/perl-buildroot/usr/lib/perl5/i386-linux/bits/syslog.ph line 9, near ", ..."
> > # /usr/src/tmp/perl-buildroot/usr/lib/perl5/i386-linux/bits/syslog.ph: deparse failed, trying to recover with -Mbits
>
> h2ph не понимает макросов с перменным списокм аргументов, а с
> FORTIFY_SOURCE теперь в /usr/include/bits/syslog.h вижу:
>
> 25 extern void __syslog_chk (int __pri, int __flag, __const char *__fmt, ...)
> 26 __attribute__ ((__format__ (__printf__, 3, 4)));
> 27
> 28 #define syslog(pri, ...) \
> 29 __syslog_chk (pri, __USE_FORTIFY_LEVEL - 1, __VA_ARGS__)
>
> Научить h2ph понимать такие макросы мне слабо. Впрочем он и так такие
> простыни на свет производит, что спасать мне его и не хочется. В общем
> во время фриза непонятно что со всем этим делать. Удалю-ка я все эти
> *.ph и будь что будет.
А зачем эти *.ph нужны? Что делают другие перловоды?
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-08 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 19:43 ` Alexey Tourbin
2006-10-08 20:02 ` Dmitry V. Levin [this message]
2006-10-08 20:44 ` Alexey Tourbin
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=20061008200238.GA13391@basalt.office.altlinux.org \
--to=ldv@altlinux.org \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git