From: Michael Shigorin <mike@osdn.org.ua> To: devel@lists.altlinux.org Subject: Re: [devel] gpart-0.1h-alt5: i586 rebuild failed [1] Date: Sat, 29 Mar 2008 17:04:28 +0200 Message-ID: <20080329150428.GD30086@osdn.org.ua> (raw) In-Reply-To: <20080329142651.BAF8B151C949@granary.armor.altlinux.org> On Sat, Mar 29, 2008 at 05:26:51PM +0300, QA Team Robot wrote: > Package: gpart-0.1h-alt5 > gcc -pipe -Wall -O2 -march=i586 -mtune=i686 -std=gnu99 -pedantic -D_LARGEFILE64_SOURCE -DVERSION=\"0.1h\" -c -o l64seek.o l64seek.c > l64seek.c:29: error: expected declaration specifiers or '...' before '_llseek' > l64seek.c:29: error: expected declaration specifiers or '...' before 'fd' > l64seek.c:29: error: expected declaration specifiers or '...' before 'hi' > l64seek.c:29: error: expected declaration specifiers or '...' before 'lo' > l64seek.c:29: error: expected declaration specifiers or '...' before 'res' > l64seek.c:29: error: expected declaration specifiers or '...' before 'wh' > l64seek.c:34: warning: return type defaults to 'int' > l64seek.c: In function '_syscall5': > l64seek.c:35: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token > l64seek.c:59: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token > l64seek.c:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token > l64seek.c:29: error: parameter name omitted > l64seek.c:80: error: expected '{' at end of input > make[1]: *** [l64seek.o] Error 1 2 kas: это мне в main/g/gpart/gpart_0.1h-4.1.diff.gz, так? -- ---- WBR, Michael Shigorin <mike@altlinux.ru> ------ Linux.Kiev http://www.linux.kiev.ua/
next parent reply other threads:[~2008-03-29 15:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-29 15:04 ` Michael Shigorin [this message] 2008-03-29 18:32 ` Kirill A. Shutemov 2008-03-29 21:30 ` [devel] gpart for sale, needs syscall-related build fix Michael Shigorin 2008-03-30 9:28 ` Grigory Batalov 2008-03-30 17:09 ` Michael Shigorin
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=20080329150428.GD30086@osdn.org.ua \ --to=mike@osdn.org.ua \ --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