[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#287634: marked as done (masqdialer: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment)



Your message dated Sat, 02 Apr 2005 14:47:18 -0500
with message-id <E1DHoaU-0006AB-00@newraff.debian.org>
and subject line Bug#287634: fixed in masqdialer 0.5.5-9
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Dec 2004 08:49:50 +0000
>From aj@andaco.de Wed Dec 29 00:49:50 2004
Return-path: <aj@andaco.de>
Received: from d007021.adsl.hansenet.de (localhost.localdomain) [80.171.7.21] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CjZWg-0003uq-00; Wed, 29 Dec 2004 00:49:50 -0800
Received: from aj by localhost.localdomain with local (Exim 4.34)
	id 1CjZbt-0004Do-2l; Wed, 29 Dec 2004 09:55:13 +0100
To: Debian Bug Tracking System <submit@bugs.debian.org>
From: Andreas Jochens <aj@andaco.de>
Subject: masqdialer: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment
Message-Id: <E1CjZbt-0004Do-2l@localhost.localdomain>
Date: Wed, 29 Dec 2004 09:55:13 +0100
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: masqdialer
Severity: normal
Tags: patch

When building 'masqdialer' on amd64 with gcc-4.0,
I get the following error:

gcc -DHAVE_CONFIG_H -I. -I. -I..     -O2 -Wall   -c authgen.c
authgen.c: In function 'main':
authgen.c:78: error: invalid lvalue in assignment
make[3]: *** [authgen.o] Error 1
make[3]: Leaving directory `/masqdialer-0.5.5/authgen'

With the attached patch 'masqdialer' can be compiled
on amd64 using gcc-4.0.

Regards
Andreas Jochens

diff -urN ../tmp-orig/masqdialer-0.5.5/authgen/authgen.c ./authgen/authgen.c
--- ../tmp-orig/masqdialer-0.5.5/authgen/authgen.c	2004-12-29 09:51:39.758911144 +0100
+++ ./authgen/authgen.c	2004-12-29 09:51:29.226512312 +0100
@@ -75,7 +75,7 @@
 	salt[1] = 'a';
 	salt[2] = '\0';
 
-	(char *) cryptpass = (char *) crypt(passwd, salt);
+	cryptpass = (char *) crypt(passwd, salt);
 
 	chomp (username);
 	chomp (cryptpass);

---------------------------------------
Received: (at 287634-close) by bugs.debian.org; 2 Apr 2005 19:56:09 +0000
>From katie@ftp-master.debian.org Sat Apr 02 11:56:09 2005
Return-path: <katie@ftp-master.debian.org>
Received: from gluck.debian.org [192.25.206.10] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DHoj3-0000np-00; Sat, 02 Apr 2005 11:56:09 -0800
Received: from newraff.debian.org [208.185.25.31] (mail)
	by gluck.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1DHoj2-0007al-00; Sat, 02 Apr 2005 12:56:08 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
	id 1DHoaU-0006AB-00; Sat, 02 Apr 2005 14:47:18 -0500
From: Philipp Kern <pkern@debian.org>
To: 287634-close@bugs.debian.org
X-Katie: $Revision: 1.55 $
Subject: Bug#287634: fixed in masqdialer 0.5.5-9
Message-Id: <E1DHoaU-0006AB-00@newraff.debian.org>
Sender: Archive Administrator <katie@ftp-master.debian.org>
Date: Sat, 02 Apr 2005 14:47:18 -0500
Delivered-To: 287634-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Source: masqdialer
Source-Version: 0.5.5-9

We believe that the bug you reported is fixed in the latest version of
masqdialer, which is due to be installed in the Debian FTP archive:

masqdialer_0.5.5-9.diff.gz
  to pool/main/m/masqdialer/masqdialer_0.5.5-9.diff.gz
masqdialer_0.5.5-9.dsc
  to pool/main/m/masqdialer/masqdialer_0.5.5-9.dsc
masqdialer_0.5.5-9_i386.deb
  to pool/main/m/masqdialer/masqdialer_0.5.5-9_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 287634@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern <pkern@debian.org> (supplier of updated masqdialer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat,  2 Apr 2005 19:14:53 +0000
Source: masqdialer
Binary: masqdialer
Architecture: source i386
Version: 0.5.5-9
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Philipp Kern <pkern@debian.org>
Description: 
 masqdialer - daemon for remote control of masqueraded dialup links
Closes: 287634 300283
Changes: 
 masqdialer (0.5.5-9) unstable; urgency=low
 .
   * QA upload.
   * Applied fixes for FTBFS on amd64/gcc-4.0, thanks to Andreas Jochens.
     (Closes: #287634, #300283)
   * Fixed various lintian warnings and errors.
Files: 
 c8ffee157d337915a06224879303e144 637 net optional masqdialer_0.5.5-9.dsc
 5ee764a40a3fadb3d1a5640ba5619915 40664 net optional masqdialer_0.5.5-9.diff.gz
 46a0e19e5772a6a1d67ce3f36786fc87 116274 net optional masqdialer_0.5.5-9_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)
Comment: Signed and encrypted mails welcome...

iEYEARECAAYFAkJO8RwACgkQ7Ro5M7LPzdgIQACdEGEfEfeNCUpKu4+YRo6OOlr3
AYsAnRRlr7drQN5yDO0yrXUyGLYFs6jT
=75qL
-----END PGP SIGNATURE-----



Reply to: