Debian Bug report logs - #8241
dpkg --print-architecture broken

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: bruce@pixar.com (Bruce Perens)

To: submit@bugs.debian.org, klee@mit.edu

Subject: dpkg --print-architecture broken

Date: Fri, 21 Mar 97 21:48 PST

Package: dpkg
Version: 1.4.0.8

I have gcc 2.7.2.1-7 installed. Dpkg --print-architecture is broken by
an interaction with gcc.

# dpkg --print-architecture
dpkg: unexpected output from `gcc --print-libgcc-file-name':
 `/usr/lib/libgcc.a'
dpkg: compiler libgcc filename not understood: no gcc-lib component

Most packages won't build because of this.

	Thanks

	Bruce
-- 
Bruce Perens K6BP   Bruce@Pixar.com   510-215-3502
Finger bruce@master.Debian.org for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6  1F 89 6A 76 95 24 87 B3 

Message #10 received at 8241@bugs.debian.org (full text, mbox, reply):

From: Galen Hazelwood <galenh@micron.net>

To: Bruce Perens <bruce@pixar.com>, 8241@bugs.debian.org

Subject: Re: Bug#8241: dpkg --print-architecture broken

Date: Fri, 21 Mar 1997 23:25:21 -0700

Bruce Perens wrote:
> 
> Package: dpkg
> Version: 1.4.0.8
> 
> I have gcc 2.7.2.1-7 installed. Dpkg --print-architecture is broken by
> an interaction with gcc.
> 
> # dpkg --print-architecture
> dpkg: unexpected output from `gcc --print-libgcc-file-name':
>  `/usr/lib/libgcc.a'
> dpkg: compiler libgcc filename not understood: no gcc-lib component
> 
> Most packages won't build because of this.
> 

With dpkg 1.4.0.8 and gcc 2.7.2.1-7, I get:

bash-2.00$ gcc --print-libgcc-file-name
/usr/lib/gcc-lib/i486-linux/2.7.2.2/libgcc.a
bash-2.00$ dpkg --print-architecture
i386
bash-2.00$

I suggest you check your /usr/lib for a spurious libgcc.a file.

--Galen

Message #15 received at 8241@bugs.debian.org (full text, mbox, reply):

From: bruce@pixar.com (Bruce Perens)

To: 8241@bugs.debian.org, Bruce Perens <bruce@pixar.com>, Galen Hazelwood <galenh@micron.net>

Subject: Re: Bug#8241: dpkg --print-architecture broken

Date: Fri, 21 Mar 97 22:36 PST

It's this:

diversion by gnat from: /usr/lib/gcc-lib/i486-linux/2.7.2/libgcc.a
diversion by gnat to: /usr/lib/gcc-lib/i486-linux/2.7.2/libgcc.a.orig-gcc
diversion by gnat from: /usr/lib/gcc-lib/i486-linux/2.7.2/libgcc.a
diversion by gnat to: /usr/lib/gcc-lib/i486-linux/2.7.2/libgcc.a.orig-gcc
gcc: /usr/lib/gcc-lib/i486-linux/2.7.2.1/libgcc.a
win32gcc: /usr/lib/gcc-lib/i386-unknown-cygwin32/cygnus-2.7.2-960712/libgcc.a

Gnat diverted my C library, and installed a C library in another compiler
version's directory, and this old /usr/lib/libgcc.a happened to be there,
but it's still broken if I remove that. Un-doing the diversion fixes it.

Is this dpkg's fault for doing a bad diversion, or gnat's fault?

	Thanks

	Bruce
-- 
Bruce Perens K6BP   Bruce@Pixar.com   510-215-3502
Finger bruce@master.Debian.org for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6  1F 89 6A 76 95 24 87 B3 

Message #20 received at 8241@bugs.debian.org (full text, mbox, reply):

From: nakahara@mis.hiroshima-u.ac.jp (Hayao Nakahara)

To: galenh@micron.net, 8241@bugs.debian.org

Cc: bruce@pixar.com, 8241@bugs.debian.org

Subject: Re: Bug#8241: dpkg --print-architecture broken

Date: Mon, 31 Mar 1997 11:22:56 +0900 (JST)

> Galen Hazelwood <galenh@micron.net> wrote:

 > Bruce Perens wrote:
 > > 
 > > Package: dpkg
 > > Version: 1.4.0.8
 > > 
 > > I have gcc 2.7.2.1-7 installed. Dpkg --print-architecture is broken by
 > > an interaction with gcc.
 > > 
 > > # dpkg --print-architecture
 > > dpkg: unexpected output from `gcc --print-libgcc-file-name':
 > >  `/usr/lib/libgcc.a'
 > > dpkg: compiler libgcc filename not understood: no gcc-lib component
 > > 
 > > Most packages won't build because of this.
 > > 
 > 
 > With dpkg 1.4.0.8 and gcc 2.7.2.1-7, I get:
 > 
 > bash-2.00$ gcc --print-libgcc-file-name
 > /usr/lib/gcc-lib/i486-linux/2.7.2.2/libgcc.a
 > bash-2.00$ dpkg --print-architecture
 > i386
 > bash-2.00$
 > 
 > I suggest you check your /usr/lib for a spurious libgcc.a file.
 > 
 > --Galen

The proble is that dpkg is often invoked when gcc is not installed.

For example, I prefere to use experimental package dpkg-mountable
which uses "dpkg --print-architecture". Usining dselect with mountable
method at initial install time always fails.  

-- 
Hayao Nakahara
Hiroshima University nakahara@mis.hiroshima-u.ac.jp

Message #29 received at 8241@bugs.debian.org (full text, mbox, reply):

From: Cyrille Chepelov <chepelov@calixo.net>

To: 8241@bugs.debian.org

Subject: works for me

Date: Wed, 25 Jul 2001 14:32:30 +0200

with dpkg 1.9.16, gcc 2.95.4, gnat 3.13p-18

I assume it should be OK to close it in two weeks.

Message #36 received at 8241-done@bugs.debian.org (full text, mbox, reply):

From: Thomas Hood <jdthood@yahoo.co.uk>

To: 8241-done@bugs.debian.org

Subject: done, I presume

Date: 01 Oct 2002 10:43:09 +0200

> I assume it should be OK to close it in two weeks.

This unreproducible bug appears to have resulted from
a faulty diversion which was reported to be fixed by
later releases of gcc and/or gnat (see previous message).

Closing this.  Please reopen if there is still a problem here.

--
Thomas

Send a report that this bug log contains spam.