On Wed, Oct 04, 2000 at 02:58:44PM +0000, Piotr Roszatycki wrote: > On 4 Oct 2000 16:40:48 +0200, Ben Collins <[EMAIL PROTECTED]> wrote: > >> >That means your gcc build is broken, you can't blame dpkg for that. > >> > >> Why we can't make a workaround for that? > > > >Your the one with the broken system...be my guest :) > > Gee, this is gnuizm :) > > What do you think about > ./configure --with-broken-libgcc ?
Why not just add checks in the query to notice the error? Print an error to stderr and fallback to build-arch on stdout? That will atleast cause it to get a default but still print output usable by the caller. -- -----------=======-=-======-=========-----------=====------------=-=------ / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=========------=======-------------=-=-----=-===-======-------=--=---'
