Home > Archive > Tcl > October 2006 > Problem building all of tcllib 1.9
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problem building all of tcllib 1.9
|
|
|
| Hello,
I'm trying to build tcllib-1.9 but I'm encountering a number of
failures. I'm using FreeBSD 6.1 with Tcl 8.4.13 built with threads (for
AOLserver).
The FreeBSD port of tcllib is some way behind at version 1.7, so I've
made my own port for 1.9. Changing the port to 1.9 is trivial, and I
don't think that's the problem as I get exactly the same results if I
build using ./configure, etc.
During the tests stage it shows the following failures:
[ ] [8.4.13] fileutil ~~ FAILS T 314 P 285 S 2 F 27
[ ] [8.4.13] mime ~~ FAILS T 49 P 46 S 0 F 3
[ ] [8.4.13] tie ~~ FAILS T 223 P 105 S 4 F 114
And at the end:
Passed 13295 of 13686
Skipped 247 of 13686
Failed 144 of 13686
#Errors 0
If I build version 1.7 from ports it actually shows the following:
Total 8622
Passed 8395
Skipped 142
Failed 85
Is there some way to find out what all the failures are? I've looked for
a log file but I can't seem to find one. I've also looked on the tcllib
wiki, Google, etc.
Thanks,
Frem.
| |
| Michael Schlenker 2006-10-06, 7:02 pm |
| Frem schrieb:
> Hello,
>
> I'm trying to build tcllib-1.9 but I'm encountering a number of
> failures. I'm using FreeBSD 6.1 with Tcl 8.4.13 built with threads (for
> AOLserver).
>
> The FreeBSD port of tcllib is some way behind at version 1.7, so I've
> made my own port for 1.9. Changing the port to 1.9 is trivial, and I
> don't think that's the problem as I get exactly the same results if I
> build using ./configure, etc.
>
> During the tests stage it shows the following failures:
> [ ] [8.4.13] fileutil ~~ FAILS T 314 P 285 S 2 F 27
> [ ] [8.4.13] mime ~~ FAILS T 49 P 46 S 0 F 3
> [ ] [8.4.13] tie ~~ FAILS T 223 P 105 S 4 F 114
>
> And at the end:
> Passed 13295 of 13686
> Skipped 247 of 13686
> Failed 144 of 13686
> #Errors 0
>
> If I build version 1.7 from ports it actually shows the following:
> Total 8622
> Passed 8395
> Skipped 142
> Failed 85
>
> Is there some way to find out what all the failures are? I've looked for
> a log file but I can't seem to find one. I've also looked on the tcllib
> wiki, Google, etc.
Yes, its possible.
Sorry to see the failures only this time.
If you have a cvs checkout of the tcllib sources do the following:
cd tcllib
tclsh sak.tcl test run -l logfile
Now the tests run and you should see a some new files named logfile.xxx.
If you want more options try running ./sak.tcl test help, which should
show you some more options for running the tests.
Please file a bug report at the sourceforge tcllib bugtracker and attach
those logfiles, so the developers can see what breaks.
( ly nearly no one seems to test release candidates, those bug reports
only show up when the release was already done..., always...)
Michael
| |
|
| Michael,
Michael Schlenker wrote:
> Yes, its possible.
> Sorry to see the failures only this time.
>
> If you have a cvs checkout of the tcllib sources do the following:
>
> cd tcllib
> tclsh sak.tcl test run -l logfile
>
> Now the tests run and you should see a some new files named logfile.xxx.
Ah yes, very useful! Thanks very much.
I've now found the problem with all the fileutil and tie tests. When
building ports on FreeBSD, one needs to be root as the ports directories
are owned by root. If I chown my port to my local user, and build as me
then the problems with fileutil and tie go away. That just leaves 3 mime
tests which still fail:
Passed 13436 of 13686
Skipped 247 of 13686
Failed 3 of 13686
#Errors 0
It would appear that something in ::tcltest::makeFile is awry for the
fileutil and tie tests. Not sure about the mime ones.
> If you want more options try running ./sak.tcl test help, which should
> show you some more options for running the tests.
>
> Please file a bug report at the sourceforge tcllib bugtracker and attach
> those logfiles, so the developers can see what breaks.
I'll do that.
> (ly nearly no one seems to test release candidates, those bug reports
> only show up when the release was already done..., always...)
We're all guilty of that, I guess.
> Michael
Frem.
| |
| Michael Schlenker 2006-10-08, 8:07 am |
| Frem schrieb:
> Michael,
>
> Michael Schlenker wrote:
>
> Ah yes, very useful! Thanks very much.
>
> I've now found the problem with all the fileutil and tie tests. When
> building ports on FreeBSD, one needs to be root as the ports directories
> are owned by root. If I chown my port to my local user, and build as me
> then the problems with fileutil and tie go away.
Running the tests as root isn't the best idea, no idea what exactly
fails then.
Michael
|
|
|
|
|