Bug 799 - error while compiling
Summary: error while compiling
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Build environment (show other bugs)
Version: 3.0.0
Hardware: All Linux
: P3 normal
Target Milestone: none
Assignee: Tim Potter
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-21 01:22 UTC by Packetloss
Modified: 2005-11-14 09:31 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Packetloss 2003-11-21 01:22:18 UTC
Hi,

Some info:
root@tommie:~# gcc --version
gcc (GCC) 3.2.3
root@tommie:~# uname -a
Linux tommie 2.4.22 #2 Wed Nov 19 21:44:46 CET 2003 i686 unknown unknown 
GNU/Linux
root@tommie:~# cat /etc/slackware-version
Slackware 9.1.0

It is a 'clean' Slackware install, execpt the installation from source of
ntp-4.2.0, procmail-3.22, rsync-2.5.6, joe-2.9.8 and arpwatch-2.1a11.

I downloaded Samba from: ftp://ftp.easynet.be/samba/samba-3.0.0.tar.gz.


So, I'm compiling from source. The first error I got was:

Compiling rpc_parse/parse_ds.c
Compiling rpc_parse/parse_spoolss.c
rpc_parse/parse_spoolss.c: In function `smb_io_doc_info_1':
rpc_parse/parse_spoolss.c:119: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make: *** [rpc_parse/parse_spoolss.o] Error 1


then I tried to `make` samba again. Then I got this one:

Compiling rpc_parse/parse_spoolss.c
rpc_parse/parse_spoolss.c: In function `smb_io_printer_info_4':
rpc_parse/parse_spoolss.c:2633: syntax error before "if"
make: *** [rpc_parse/parse_spoolss.o] Error 1

So, I edited the end of line 2633 of rpc_parse/parse_spoolss.c. There I found 
a '+', and edited it to a ';'.

Then `make` didn't complain anymore.

If you need more info, do not hesitate to contact me.
Comment 1 Tim Potter 2003-11-21 02:27:37 UTC
X-Original-To: tpot@samba.org
From: "O.E. van Ouwerkerk" <otto@vanouwerkerk.com>
X-X-Sender: otto@kermit.haarweg.nl
To: tpot@samba.org
Subject: bugID 799
                                                                                
Hi Tim,
                                                                                
Concerning bugID 799, I made a typo. It wasn't line #2633 I edited, but
line #2632. Sorry :(.
                                                                                
                                                                                
Otto
Comment 2 Tim Potter 2003-11-25 15:13:24 UTC
A signal 11 during compilation is either a bug in the compiler, or bad hardware.
 See http://www.bitwizard.nl/sig11/ for details.

The file you mention doesn't contain a + symbol at the line you mention.  Are
you sure you have an uncorrupted archive?  Can you verify the checksum of the
file you downloaded?

The signature file is at http://us1.samba.org/samba/ftp/samba-3.0.0.tar.asc and
you need to uncompress the tar file and run gpg like:

[tpot@nevada:/data]$ gpg --verify samba-3.0.0.tar.asc samba-3.0.0.tar
gpg: Signature made Thu 25 Sep 2003 11:54:24 EST using DSA key ID 2F87AF6F
gpg: Good signature from "Samba Distribution Verification Key
<samba-bugs@samba.org>"
gpg: checking the trustdb
gpg: no ultimately trusted keys found
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 3275 F01D 6565 3A81 AE7B  320C D779 0A5F 2F87 AF6F
Comment 3 Packetloss 2003-11-26 00:05:58 UTC
> The file you mention doesn't contain a + symbol at the line you mention.
I know.. But I'm 100% sure it was there, otherwise I wouldn't have got the error
rpc_parse/parse_spoolss.c:2633: syntax error before "if"

> Are you sure you have an uncorrupted archive?  Can you verify the checksum
> of the file you downloaded?
Yes, I certainly did.
Comment 4 Tim Potter 2003-11-26 14:33:08 UTC
Well I can't explain what has happened here!  There's no sign of a syntax error
in the archive you downloaded.  The only thing I can think of is some
memory/disk corruption when unpacking the archive.  The signal 11 during
compilation does suggest you may have some hardware issues.
Comment 5 Gerald (Jerry) Carter (dead mail address) 2005-11-14 09:31:03 UTC
database cleanup