From: Upravdom Team Robot <upravdom@altlinux.org>
To: "Alexey I. Froloff (Sir Raorn)" <raorn@altlinux.org>
Cc: sisyphus-incominger@lists.altlinux.org
Subject: [Sisyphus-incominger] E: incoming i586 reject: vim-7.0.010-alt1
Date: Fri, 12 May 2006 05:49:02 +0400 (MSD)
Message-ID: <20060512014902.D81D4F6CD@mash.office.altlinux.ru> (raw)
Dear Alexey I. Froloff (Sir Raorn) !
The vim-7.0.010-alt1 package has been rejected from incoming for i586
architecture.
Possible reason follows:
i586-alt-linux-gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_ATHENA -DFEAT_GUI_NEXTAW -DFUNCPROTO=15 -DNARROWPROTO -pipe -Wall -O2 -march=i586 -mtune=pentium4 -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I/usr/lib/perl5/i386-linux/CORE -I/usr/include/python2.4 -pthread -I/usr/include -D_LARGEFILE64_SOURCE=1 -I/usr/include/ruby/1.8 -o objects/gui_at_fs.o gui_at_fs.c
gui_at_fs.c: In function 'SFvAreaSelectedCallback':
gui_at_fs.c:1872: error: invalid lvalue in assignment
gui_at_fs.c:1874: error: invalid lvalue in assignment
gui_at_fs.c:1879: error: invalid lvalue in assignment
gui_at_fs.c:1881: error: invalid lvalue in assignment
gui_at_fs.c: In function 'SFhAreaSelectedCallback':
gui_at_fs.c:1952: error: invalid lvalue in assignment
gui_at_fs.c:1954: error: invalid lvalue in assignment
gui_at_fs.c:1959: error: invalid lvalue in assignment
gui_at_fs.c:1961: error: invalid lvalue in assignment
gui_at_fs.c: In function 'SFpathAreaSelectedCallback':
gui_at_fs.c:2048: error: invalid lvalue in assignment
gui_at_fs.c:2050: error: invalid lvalue in assignment
gui_at_fs.c:2055: error: invalid lvalue in assignment
gui_at_fs.c:2057: error: invalid lvalue in assignment
make: *** [objects/gui_at_fs.o] Error 1
make: Leaving directory `/usr/src/RPM/BUILD/vim70/src'
error: Bad exit status from /usr/src/tmp/rpm-tmp.10583 (%build)
RPM build errors:
Unparseable macro: % and # in tags file path
Bad exit status from /usr/src/tmp/rpm-tmp.10583 (%build)
1242.10user 125.95system 22:41.85elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (3058489major+8376577minor)pagefaults 0swaps
rebuild: rebuild of `vim-7.0.010-alt1.src.rpm' failed.
removed `/tmp/.private/bee5/workdir/lockdir/pid'
removed directory: `/tmp/.private/bee5/workdir/lockdir'
--
Rgrds, your upravdom
reply other threads:[~2006-05-12 1:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060512014902.D81D4F6CD@mash.office.altlinux.ru \
--to=upravdom@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=raorn@altlinux.org \
--cc=sisyphus-incominger@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 Girar Builder robot reports
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus-incominger/0 sisyphus-incominger/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 sisyphus-incominger sisyphus-incominger/ http://lore.altlinux.org/sisyphus-incominger \
sisyphus-incominger@lists.altlinux.org sisyphus-incominger@lists.altlinux.ru sisyphus-incominger@lists.altlinux.com
public-inbox-index sisyphus-incominger
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-incominger
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git