Re: [Zope3-Users] Installation Erros

2005-07-14 Thread Tim Peters
[Tim Cook, finds his 3.1.0b1 problem]
> ...
> The problem REALLY wasMidnight Commander.
> I have used mc for many years and never seen this before.  But by using
> tar on the commandline the file extracted fine and I now a bright shiny
> instance of Zope3 running.

I hope someone pursues it anyway.  Various Zope-ish distributions hit
tar problems several times per year, and I don't know for a fact that
it's necessary for "us" to use a specific tar program in such a way
that other tar programs can't deal with the tarballs.  Anyone up to
date on their tar lore (I'm sure not)?

> Still had the gcc4 warnings but no biggie there.

Repairing that is adding a pile of tedious casting to C code mostly
under my care these days.  Since I don't have gcc4 and don't have
spare time to install it just for this, it would be nice if someone
with gcc4 submitted a patch.  It should be easy (if dull) -- adding
(char *) casts to the arguments gcc4 is complaining about.

> Sorry for the hassle and certainly for the big leap to tarball
> judgement.

Hey, from your POV the tarball _was_ broken.
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] Installation Erros

2005-07-14 Thread Tim Cook
On Thu, 2005-07-14 at 17:34 -0400, Tim Peters wrote:

> > Obviously someone needs to create a new Linux distribution, eh! 
> 
> Nope, because nobody else has reported this.  What are the odds that
> you're the only one who has used the tarball?  I don't know, but
> they're not high .

I must admit this crossed my mind.  I really jumped to a huge conclusion
there.

I had checked the md5sum just to be sure it wasn't a bad download.

The problem REALLY wasMidnight Commander.
I have used mc for many years and never seen this before.  But by using
tar on the commandline the file extracted fine and I now a bright shiny
instance of Zope3 running.  Still had the gcc4 warnings but no biggie
there.

Sorry for the hassle and certainly for the big leap to tarball
judgement.

Cheers,
-- 
Tim Cook



signature.asc
Description: This is a digitally signed message part
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] Installation Erros

2005-07-14 Thread Tim Peters
[Tim Cook]
>>> Installing Zope-3.1.0b1 on Fedora Core 4
>>>
>>> gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8)

[and problems with "make check"]

[Tim Cook]
> I finally had a chance to look at this again.  The original results are
> attached in a text file.  The problem is that there are several source
> files that end in .p instead of .py.
>
> My first clue was the first lines that said these tests weren't
> packages.  I thought someone just forgot the init files.  Nope, they
> were there, just missing a y in the filename.
> 
> There are also misnamed .html and .stx files.  Same problem, dropped
> last character.
> 
> I checked the archive (Zope-3.1.0b1.tgz) and the files are misnamed in
> there.
> 
> Obviously someone needs to create a new Linux distribution, eh! 

Nope, because nobody else has reported this.  What are the odds that
you're the only one who has used the tarball?  I don't know, but
they're not high .

I don't know how the tarball was built originally, but I built the
Windows installers _from_ the tarball and had no problems.  I imagine
it was built with GNU tar, and that has a history of creating problems
(due to GNU extensions) for other tar implementations.  Did you use
GNU tar to unpack it?  If not, try that.  Or perhaps you got a corrupt
download (did you check the MD5 against the one listed?).

As a check, I just downloaded the tarball fresh from

http://www.zope.org/Products/Zope3/3.1.0b1

to a Linux box, and used its tar to unpack it:

$ tar --version
tar (GNU tar) 1.13.25


$ tar xvzf Zope-3.1.0b1.tgz
... [lots of output] ...

$ find Zope-3.1.0b1 -name "*.py" | wc -l
   2429
$ find Zope-3.1.0b1 -name "*.p"
$

That is, there are no .p files.  You didn't give enough info about the
other badly named files for me to check, but I doubt I'd find any
other damage here either.  I went on to do ./configure, make, and
`make check` without problems:

$ make check
/usr/local/bin/python install.py -q build
/usr/local/bin/python test.py -v
Running UNIT tests at level 1
Running UNIT tests from /home/tim/Zope-3.1.0b1/build/lib.linux-i686-2.3
...
[lots of dots]
Ran 6831 tests in 236.672s

OK
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] Installation Erros

2005-07-14 Thread Tim Cook
On Sat, 2005-07-09 at 09:49 -0400, Tim Peters wrote:
> [Tim Cook]
> > Installing Zope-3.1.0b1 on Fedora Core 4
> > 
> > gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8)
> 
...

> This is the only interesting part.  It might help if you posted again,
> skipping all the compiler warnings (which aren't interesting), and
> gave the full output from `make check`.

Hi All,

I finally had a chance to look at this again.  The results are
in a text file on Zope.org. (it was too large to post to the list)
http://www.zope.org/Members/tcook/check_results 
I'm not sure how soon it will be published.

The problem is that there are several source files that end in .p instead of 
.py.

My first clue was the first lines that said these tests weren't
packages.  I thought someone just forgot the init files.  Nope, they
were there, just missing a y in the filename. 

There are also misnamed .html and .stx files.  Same problem, dropped
last character.

I checked the archive (Zope-3.1.0b1.tgz) and the files are misnamed in
there. 

Obviously someone needs to create a new Linux distribution, eh! 

Cheers,
-- 
Tim Cook


signature.asc
Description: This is a digitally signed message part
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] Installation Erros

2005-07-09 Thread Fred Drake
On 7/9/05, Tim Peters <[EMAIL PROTECTED]> wrote:
> While I doubt it matters, it's possible that some bug in gcc4 is
> creating actual problems.  Trying again with an earlier version of gcc
> would settle that question.  Since (AFAIK) nobody before mentioned the
> pile of new warnings gcc4 produces, it's possible you're the first to
> try Zope's C code under gcc4.

It may also be interesting to try with the version of GCC 4 that just
came out this week; GCC 4.0.1 came out on Thursday.  If there are any
GCC 4 bugs, those may have been fixed with that release.


  -Fred

-- 
Fred L. Drake, Jr.
Zope Corporation
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


Re: [Zope3-Users] Installation Erros

2005-07-09 Thread Tim Peters
[Tim Cook]
> Installing Zope-3.1.0b1 on Fedora Core 4
>
> I didn't see these erros in any previous mailing list post nor did I
> find a bug collector.
> 
> 
> gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8)

All the compilation warnings you got were due to using gcc4; they're
nuisance complaints, essentially complaining about that gcc4 itself
decides to treat an unqualified "char" declaration as if it were
"signed char".  This means you get a nuisance nag whenever C code
passes an "unsigned char *" to PyString_FromStringAndSize, which
declares its pointer-to-char argument as plain "char *", because
PyString_FromStringAndSize couldn't care less whether the box decides
to treat unqualifed char as signed or unsigned (C doesn't define which
they are -- it's the compiler's choice).

Adding a pile of annoying casting to the C code will make those
warnings go away, but they're not pointing out any real problems, so
ignore them.

> installed python version 2.3.5 prior to attempting install of Zope3.

[skipped a mass of nags about calls to PyString_FromStringAndSize]

> ..and the last several lines of 'make check'

This is the only interesting part.  It might help if you posted again,
skipping all the compiler warnings (which aren't interesting), and
gave the full output from `make check`.

While I doubt it matters, it's possible that some bug in gcc4 is
creating actual problems.  Trying again with an earlier version of gcc
would settle that question.  Since (AFAIK) nobody before mentioned the
pile of new warnings gcc4 produces, it's possible you're the first to
try Zope's C code under gcc4.
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users


[Zope3-Users] Installation Erros

2005-07-08 Thread Tim Cook
Installing Zope-3.1.0b1 on Fedora Core 4

I didn't see these erros in any previous mailing list post nor did I
find a bug collector.


gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8)
installed python version 2.3.5 prior to attempting install of Zope3.

Not a pretty picture as you see below.

Any help is appreciated.

Thanks,
Tim

***

bash-3.00$ ./configure

Configuring Zope 3 installation

Testing for an acceptable Python interpreter...

Python version 2.3.5 found at /usr/local/bin/python

The optimum Python version (2.3.5) was found at /usr/local/bin/python.

bash-3.00$ make
/usr/local/bin/python install.py -q build
Dependencies/persistent-Zope-3.1.0b1/persistent/TimeStamp.c: In function
‘TimeStamp_raw’:
Dependencies/persistent-Zope-3.1.0b1/persistent/TimeStamp.c:221:
warning: pointer targets in passing argument 1 of
‘PyString_FromStringAndSize’ differ in signedness
Dependencies/persistent-Zope-3.1.0b1/persistent/TimeStamp.c: In function
‘TimeStamp_laterThan’:
Dependencies/persistent-Zope-3.1.0b1/persistent/TimeStamp.c:264:
warning: pointer targets in passing argument 1 of ‘TimeStamp_FromString’
differ in signedness
In file included from
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeModuleTemplate.c:335,
 from
Dependencies/BTrees-Zope-3.1.0b1/BTrees/_fsBTree.c:70:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeItemsTemplate.c: In
function ‘getBucketEntry’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeItemsTemplate.c:238:
warning: pointer targets in passing argument 1 of
‘PyString_FromStringAndSize’ differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeItemsTemplate.c:242:
warning: pointer targets in passing argument 1 of
‘PyString_FromStringAndSize’ differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeItemsTemplate.c:249:
warning: pointer targets in passing argument 1 of
‘PyString_FromStringAndSize’ differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeItemsTemplate.c:252:
warning: pointer targets in passing argument 1 of
‘PyString_FromStringAndSize’ differ in signedness
In file included from
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeModuleTemplate.c:336,
 from
Dependencies/BTrees-Zope-3.1.0b1/BTrees/_fsBTree.c:70:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c: In function
‘_bucket_get’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:93: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c: In function
‘Bucket_maxminKey’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:705: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c: In function
‘bucket_keys’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:817: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c: In function
‘bucket_values’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:855: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c: In function
‘bucket_items’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:895: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:899: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c: In function
‘bucket_byValue’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:943: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:949: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c: In function
‘bucket_getstate’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:1122: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:1128: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BucketTemplate.c:1139: warning:
pointer targets in passing argument 1 of ‘PyString_FromStringAndSize’
differ in signedness
In file included from
Dependencies/BTrees-Zope-3.1.0b1/BTrees/BTreeModuleTemplate.c:337,
 from
Dependencies/BTrees-Zope-3.1.0b1/BTrees/_fsBTree.c:70:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/SetTemplate.c: In function
‘set_item’:
Dependencies/BTrees-Zope-3.1.0b1/BTrees/SetTemplate.c