Report forwarded to debian-bugs-dist@lists.debian.org, Ian Jackson <ian@chiark.greenend.org.uk>:
Bug#9690; Package dpkg.   debian-bugs-dist@lists.debian.orgIan Jackson  Subject: Bug#9690: dpkg: Hidden dependency on gcc Reply-To: John Goerzen , 9690@bugs.debian.org Resent-From: John Goerzen Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Ian Jackson Resent-Date: Fri, 09 May 1997 17:03:01 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 9690 X-Debian-PR-Package: dpkg X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by bugs@bugs.debian.org id=B.8631970181095 (code B ref -1); Fri, 09 May 1997 17:03:01 GMT Date: Fri, 9 May 1997 11:56:50 -0500 From: John Goerzen Message-Id: <199705091656.LAA08784@happy.cs.twsu.edu> To: jgoerzen@happy.cs.twsu.edu, submit@bugs.debian.org Package: dpkg Version: 1.4.0.7 Displays: dpkg (subprocess): failed to exec C compiler `gcc': No such file or directory dpkg: subprocess gcc --print-libgcc-file-name returned error exit status 2 I don't have gcc and don't want to have to have it on this system. There is no reason that dpkg should require it. The above message was displayed when I selected "update". -- System Information Debian Release: 1.2 Kernel Version: Linux happy 2.0.25 #1 Fri Feb 28 16:49:31 CST 1997 i386 Versions of the packages dpkg depends on: libc5 Version: 5.4.20-1 ncurses3.0 Version: 1.9.9e-1   Acknowledgement sent to John Goerzen <jgoerzen@happy.cs.twsu.edu>:
New bug report received and forwarded. Copy sent to Ian Jackson <ian@chiark.greenend.org.uk>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: John Goerzen Subject: Bug#9690: Acknowledgement (was: dpkg: Hidden dependency on gcc) Message-ID: In-Reply-To: <199705091656.LAA08784@happy.cs.twsu.edu> References: <199705091656.LAA08784@happy.cs.twsu.edu> X-Debian-PR-Message: ack 9690 Thank you for the problem report you have sent regarding Debian Linux. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the developers' mailing list for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Ian Jackson If you wish to submit further information on your problem, please send it to 9690@bugs.debian.org (and *not* to bugs@bugs.debian.org). Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at submit) by bugs.debian.org; 9 May 1997 16:56:58 +0000 Received: (qmail 1093 invoked from network); 9 May 1997 16:56:57 -0000 Received: from happy.cs.twsu.edu (jgoerzen@156.26.10.161) by master.debian.org with SMTP; 9 May 1997 16:56:57 -0000 Received: (from jgoerzen@localhost) by happy.cs.twsu.edu (8.8.5/8.8.5) id LAA08784; Fri, 9 May 1997 11:56:50 -0500 Date: Fri, 9 May 1997 11:56:50 -0500 From: John Goerzen Message-Id: <199705091656.LAA08784@happy.cs.twsu.edu> To: jgoerzen@happy.cs.twsu.edu, submit@bugs.debian.org Subject: dpkg: Hidden dependency on gcc Package: dpkg Version: 1.4.0.7 Displays: dpkg (subprocess): failed to exec C compiler `gcc': No such file or directory dpkg: subprocess gcc --print-libgcc-file-name returned error exit status 2 I don't have gcc and don't want to have to have it on this system. There is no reason that dpkg should require it. The above message was displayed when I selected "update". -- System Information Debian Release: 1.2 Kernel Version: Linux happy 2.0.25 #1 Fri Feb 28 16:49:31 CST 1997 i386 Versions of the packages dpkg depends on: libc5 Version: 5.4.20-1 ncurses3.0 Version: 1.9.9e-1   Information forwarded to debian-bugs-dist@lists.debian.org, Ian Jackson <ian@chiark.greenend.org.uk>:
Bug#9690; Package dpkg.   debian-bugs-dist@lists.debian.orgIan Jackson  Subject: Bug#9690: dpkg: Hidden dependency on gcc Reply-To: Klee Dienes , 9690@bugs.debian.org Resent-From: Klee Dienes Orignal-Sender: Klee Dienes Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Ian Jackson Resent-Date: Fri, 09 May 1997 19:33:02 GMT Resent-Message-ID: Resent-Sender: iwj@debian.org X-Debian-PR-Message: report 9690 X-Debian-PR-Package: dpkg X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by 9690-bugs@bugs.debian.org id=B9690.86320575623364 (code B ref 9690); Fri, 09 May 1997 19:33:02 GMT From: Klee Dienes To: John Goerzen Cc: 9690@bugs.debian.org, Andy W.P. Guy References: <199705091656.LAA08784@happy.cs.twsu.edu> Date: 09 May 1997 15:19:49 -0400 In-Reply-To: John Goerzen's message of Fri, 9 May 1997 11:56:50 -0500 Message-ID: Lines: 51 X-Mailer: Gnus v5.4.17/XEmacs 19.15 Sender: Klee Dienes John Goerzen writes: > I don't have gcc and don't want to have to have it on this system. There is > no reason that dpkg should require it. [ The following response is a repeat of my response to Bug #9089. Andy: are you still actively maintaining dpkg-ftp? If not, would you object if I made a release to fix some of the more commonly reported bugs? ] dpkg provides three different options to give architecture information about the machine on which it is run: dpkg --print-installation-architecture: This returns the architecture string for the machine on which dpkg is being run, is determined when dpkg is compiled, and is contained statically within the dpkg binary dpkg --print-architecture: This prints the Debian architecture string for the machine type for which the compile environment is currently configured to generate executable code. Typically this will be the same as the output of 'dpkg --print-installation-architecture', but it may be different when one is cross-compiling. dpkg currently uses 'gcc --print-libgc-file-name' to determine the current compilation target architecture. dpkg --print-gnu-build-architecture: The same as 'dpkg --print-architecture', except that it prints the machine component of the GNU 'configure' string for the architecture instead of the Debian architecture string. The machine component of the GNU 'configure' string will typically be the same as the Debian architecture string, except GNU uses 'i486' where Debian uses 'i386'. I agree that the hidden dependence of dpkg on gcc is less than optimal, but given that the two options in question are only designed to be used when building architecture-specific packages, I believe it to be the best available solution at the moment. Roman Hodek has recently been doing a good bit of work on cross-compilation; this may well lead to some improvements in the way dpkg is handling things. Here, though, I believe the problem to be in dpkg-ftp: I believe that line 32 of 'update' and line 31 of 'setup' should be changed to use 'dpkg --print-installation-architecture' instead of 'dpkg --print-architecture'. Accordingly, I'm reassigning this bug report to dpkg-ftp.   Acknowledgement sent to Klee Dienes <klee@mit.edu>:
Extra info received and forwarded to list. Copy sent to Ian Jackson <ian@chiark.greenend.org.uk>.   -t  From: owner@bugs.debian.org (Ian Jackson) To: Klee Dienes Subject: Bug#9690: Info received (was Bug#9690: dpkg: Hidden dependency on gcc) Message-ID: In-Reply-To: References: X-Debian-PR-Message: ack-info-maintonly 9690 Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the developer(s) and to the developers' mailing list to accompany the original report. Your message has been sent to the package maintainer(s): Ian Jackson If you wish to continue to submit further information on your problem, please send it to 9690@bugs.debian.org, as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the bug-tracking system. Ian Jackson (maintainer, Debian bug tracking system)   Received: (at 9690) by bugs.debian.org; 9 May 1997 19:22:36 +0000 Received: (qmail 23362 invoked from network); 9 May 1997 19:22:30 -0000 Received: from nhv-ct1-07.ix.netcom.com (HELO sauron.fashion-technology.com) (mail@205.184.152.39) by master.debian.org with SMTP; 9 May 1997 19:22:24 -0000 Received: from klee by sauron.fashion-technology.com with local (Exim 1.62 #1) id 0wPvCt-0001q9-00 (Debian); Fri, 9 May 1997 15:19:55 -0400 From: Klee Dienes Reply-To: Klee Dienes To: John Goerzen Cc: 9690@bugs.debian.org, Andy W.P. Guy Subject: Re: Bug#9690: dpkg: Hidden dependency on gcc References: <199705091656.LAA08784@happy.cs.twsu.edu> Date: 09 May 1997 15:19:49 -0400 In-Reply-To: John Goerzen's message of Fri, 9 May 1997 11:56:50 -0500 Message-ID: Lines: 51 X-Mailer: Gnus v5.4.17/XEmacs 19.15 Sender: Klee Dienes John Goerzen writes: > I don't have gcc and don't want to have to have it on this system. There is > no reason that dpkg should require it. [ The following response is a repeat of my response to Bug #9089. Andy: are you still actively maintaining dpkg-ftp? If not, would you object if I made a release to fix some of the more commonly reported bugs? ] dpkg provides three different options to give architecture information about the machine on which it is run: dpkg --print-installation-architecture: This returns the architecture string for the machine on which dpkg is being run, is determined when dpkg is compiled, and is contained statically within the dpkg binary dpkg --print-architecture: This prints the Debian architecture string for the machine type for which the compile environment is currently configured to generate executable code. Typically this will be the same as the output of 'dpkg --print-installation-architecture', but it may be different when one is cross-compiling. dpkg currently uses 'gcc --print-libgc-file-name' to determine the current compilation target architecture. dpkg --print-gnu-build-architecture: The same as 'dpkg --print-architecture', except that it prints the machine component of the GNU 'configure' string for the architecture instead of the Debian architecture string. The machine component of the GNU 'configure' string will typically be the same as the Debian architecture string, except GNU uses 'i486' where Debian uses 'i386'. I agree that the hidden dependence of dpkg on gcc is less than optimal, but given that the two options in question are only designed to be used when building architecture-specific packages, I believe it to be the best available solution at the moment. Roman Hodek has recently been doing a good bit of work on cross-compilation; this may well lead to some improvements in the way dpkg is handling things. Here, though, I believe the problem to be in dpkg-ftp: I believe that line 32 of 'update' and line 31 of 'setup' should be changed to use 'dpkg --print-installation-architecture' instead of 'dpkg --print-architecture'. Accordingly, I'm reassigning this bug report to dpkg-ftp.   Bug reassigned from package `dpkg' to `dpkg-ftp'. Request was from Klee Dienes <klee@mit.edu> to control@bugs.debian.org.   Received: (at control) by bugs.debian.org; 25 May 1997 15:56:47 +0000 Received: (qmail 5551 invoked from network); 25 May 1997 15:56:46 -0000 Received: from nhv-ct4-24.ix.netcom.com (HELO sauron.fashion-technology.com) (mail@205.184.152.152) by 206.190.143.161 with SMTP; 25 May 1997 15:56:45 -0000 Received: from klee by sauron.fashion-technology.com with local (Exim 1.62 #1) id 0wVfex-0002GR-00 (Debian); Sun, 25 May 1997 11:56:39 -0400 From: Klee Dienes Reply-To: Klee Dienes To: control@bugs.debian.org Subject: reassign 9690 dpkg-ftp Message-Id: Sender: Klee Dienes Date: Sun, 25 May 1997 11:56:39 -0400 reassign 9690 dpkg-ftp