Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-16 Thread Jonathan Nieder
Sergey Poznyakoff wrote: > Clint Adams ha escrit: >> The mt man page suggests that a fatal error should exit with a 2; >> mt's fatal_exit exits with a 1 (MT_EXIT_INVOP). >> >> What is truly intended here? > > The former: it shoud exit with code 2. Thanks for reporting. This patch (plus an “aut

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-14 Thread Sven Joachim
On 2010-04-06 21:28 +0200, Sven Joachim wrote: > On 2010-04-06 20:02 +0200, Clint Adams wrote: > >> On Tue, Apr 06, 2010 at 05:06:49PM +0200, Sven Joachim wrote: >>> What exactly is the problem? It seems to work for me. >> >> Furthermore -2 is building on the buildds just as it does >> in my chro

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Clint Adams
So with mine, fatal.o isn't even being linked in: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../src -I.. -I. -I.. -I../../gnu -I../gnu -I../../lib -I../lib-Wall -g -O2 -MT mt.o -MD -MP -MF .deps/mt.Tpo -c -o mt.o ../../src/mt.c ../../src/mt.c: In function 'parse_opt': ../../src/mt.c:213: warni

Bug#576637: [Bug-cpio] Re: Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Sergey Poznyakoff
Clint Adams ha escrit: > The mt man page suggests that a fatal error should exit with a 2; > mt's fatal_exit exits with a 1 (MT_EXIT_INVOP). > > What is truly intended here? The former: it shoud exit with code 2. Thanks for reporting. Regards, Sergey -- To UNSUBSCRIBE, email to debian-bug

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Clint Adams
On Tue, Apr 06, 2010 at 08:49:37PM +0200, Sven Joachim wrote: > suggests that the fatal_exit function from mt.c is the intended one, but > naming it like a function with different semantics in fatal.c is highly > confusing, to say the least. Sergey, The mt man page suggests that a fatal error sh

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Sven Joachim
On 2010-04-06 20:02 +0200, Clint Adams wrote: > On Tue, Apr 06, 2010 at 05:06:49PM +0200, Sven Joachim wrote: >> What exactly is the problem? It seems to work for me. > > Furthermore -2 is building on the buildds just as it does > in my chroot. And it still fails here, even in pbuilder. I'm att

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Sven Joachim
On 2010-04-06 17:13 +0200, Clint Adams wrote: > On Tue, Apr 06, 2010 at 05:06:49PM +0200, Sven Joachim wrote: >> What exactly is the problem? It seems to work for me. > > It complains that fatal_exit is undefined. If the original source compiled fine for you (no multiple definition error), that

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Clint Adams
On Tue, Apr 06, 2010 at 05:06:49PM +0200, Sven Joachim wrote: > What exactly is the problem? It seems to work for me. Furthermore -2 is building on the buildds just as it does in my chroot. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Tr

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Sven Joachim
On 2010-04-06 16:26 +0200, Clint Adams wrote: > On Tue, Apr 06, 2010 at 12:17:35PM +, Clint Adams wrote: >> Instead I'm going to remove fatal_exit() from mt.c, which should solve >> that problem and also return the proper error code (instead of 1). > > Well, I won't just yet, since I can't bui

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Clint Adams
On Tue, Apr 06, 2010 at 05:06:49PM +0200, Sven Joachim wrote: > What exactly is the problem? It seems to work for me. It complains that fatal_exit is undefined. I have no idea what's going on here. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubsc

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Clint Adams
On Tue, Apr 06, 2010 at 12:17:35PM +, Clint Adams wrote: > Instead I'm going to remove fatal_exit() from mt.c, which should solve > that problem and also return the proper error code (instead of 1). Well, I won't just yet, since I can't build it if I do that. -- To UNSUBSCRIBE, email to de

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Clint Adams
On Tue, Apr 06, 2010 at 11:30:32AM +0200, Sven Joachim wrote: > mt_SOURCES = \ > - mt.c\ > - fatal.c > + mt.c Instead I'm going to remove fatal_exit() from mt.c, which should solve that problem and also return the proper error code (instead of 1). -- To UNSUBSCRIBE, email to debian-bugs-rc-re

Processed: Re: Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 576637 + patch Bug #576637 [cpio] cpio: FTBFS: multiple definition of `fatal_exit' Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Deb

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-06 Thread Sven Joachim
tags 576637 + patch thanks On 2010-04-06 06:41 +0200, Sven Joachim wrote: > Package: cpio > Version: 2.11-1 > Severity: serious > > The linker complains about a multiple definition of `fatal_exit': > > , > | % LANG=C debian/rules build > | [...] > | CCLD mt > | fatal.o: In function `fatal

Bug#576637: cpio: FTBFS: multiple definition of `fatal_exit'

2010-04-05 Thread Sven Joachim
Package: cpio Version: 2.11-1 Severity: serious The linker complains about a multiple definition of `fatal_exit': , | % LANG=C debian/rules build | [...] | CCLD mt | fatal.o: In function `fatal_exit': | /usr/local/src/deb-src/cpio/cpio-2.11/obj/src/../../src/fatal.c:24: multiple definiti