Wondering if there was any change of looking at NEF to see if it tould
be difficult to convert?
Wondering if there was any change of looking at NEF to see if it
tould be difficult to convert?
Hello Sean.
21 Nov 03 17:49, you wrote to All:
Wondering if there was any change of looking at NEF to see if it
tould be difficult to convert?
You might want to talk to the person who is developing the NEF/PK
version. The source isn't available but there were several
enhancements made to it.
Hello Sean!
21 Nov 03 17:49, Sean Rima wrote to All:
Wondering if there was any change of looking at NEF to see if it
tould be difficult to convert?
Well, the needed aplibs are already in the fastlst project; maybe
that's a point to start from.
Well, the needed aplibs are already in the fastlst project; maybe
that's a point to start from.
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
Hello Sean!
22 Nov 03 22:15, Sean Rima wrote to Gerrit Kuehn:
Well, the needed aplibs are already in the fastlst project;
maybe that's a point to start from.
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
fastlst works for me under FreeBSD with gcc 3.3; which version of
fastlst do you use and what's the problem with it?
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
fastlst works for me under FreeBSD with gcc 3.3; which version of
fastlst do you use and what's the problem with it?
The version on the Husky web site
Hello Sean!
23 Nov 03 21:35, Sean Rima wrote to Gerrit Kuehn:
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
fastlst works for me under FreeBSD with gcc 3.3; which version
of fastlst do you use and what's the problem with it?
The version on the Husky web site
/Which/ website exactly? I'm maintaining the code, but I know there
are still several things left to clean up. Especially not all links on
all pages point to the most recent version of the source...
The version on the Husky web site
/Which/ website exactly? I'm maintaining the code, but I know there
are still several things left to clean up. Especially not all links
on all pages point to the most recent version of the source...
I /think/ I downloaded it from the SF pages.
Well, the needed aplibs are already in the fastlst project;
maybe that's a point to start from.
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
fastlst works for me under FreeBSD with gcc 3.3; which version of
fastlst do you use and what's the problem with it?
The version on the Husky web site
Well, the needed aplibs are already in the fastlst project;
maybe that's a point to start from.
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
fastlst works for me under FreeBSD with gcc 3.3; which version of
fastlst do you use and what's the problem with it?
The version on the Husky web site
Sean
--- GoldED+/LNX 1.1.5
* Origin: TCOB1 a BBS in Ireland (2:263/950)
Hello Sean!
26 Nov 03 11:27, Sean Rima wrote to Gerrit Kuehn:
The version on the Husky web site
/Which/ website exactly? I'm maintaining the code, but I know
there are still several things left to clean up. Especially not
all links on all pages point to the most recent version of the
source...
I /think/ I downloaded it from the SF pages.
Even on sf there are different versions: -stable, -current...
I /think/ I downloaded it from the SF pages.
Even on sf there are different versions: -stable, -current...
It would have been stable, I will try now
Hello Sean.
23 Nov 03 21:35, you wrote to Gerrit Kuehn:
Well, the needed aplibs are already in the fastlst project;
maybe that's a point to start from.
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
fastlst works for me under FreeBSD with gcc 3.3; which version
of fastlst do you use and what's the problem with it?
The version on the Husky web site
Same version fails to compile here on Debian 3.0r0, must remember to
try it on SuSE 8.0, so does fidoconfig and MsgEd gcc 2.95.4.
Hello Sean!
26 Nov 03 22:03, Sean Rima wrote to Gerrit Kuehn:
I /think/ I downloaded it from the SF pages.
Even on sf there are different versions: -stable, -current...
It would have been stable, I will try now
It would also be helpful to know the version numbers of the libs from Husky you're using and the exact error messages the compiler gives.
It would also be helpful to know the version numbers of the libs from
Husky you're using and the exact error messages the compiler gives.
I grabed the CVS and it complained so I gave up
Hello Sean!
27 Nov 03 21:57, Sean Rima wrote to Gerrit Kuehn:
It would also be helpful to know the version numbers of the libs
from Husky you're using and the exact error messages the
compiler gives.
I grabed the CVS and it complained so I gave up
Sean, -v /please/.
"My car is broken" is a rather unspecific description of a problem.
The mechanic doesn't know where to look then. So please describe in
one or two sentences how to reproduce the error and post it here (or
in fidosoft.husky). Otherwise there is no chance to fix it.
I grabed the CVS and it complained so I gave up
Sean, -v /please/.
"My car is broken" is a rather unspecific description of a problem.
The mechanic doesn't know where to look then. So please describe in
one or two sentences how to reproduce the error and post it here (or
in fidosoft.husky). Otherwise there is no chance to fix it.
ROTFL, if I could tell my mechanic what was wrong, I would fix it and save money :)))))
Anyway I will redownload the CVS over the weekend
and let you know, it is the Toy Show tonight
Hello Sean!
28 Nov 03 21:46, Sean Rima wrote to Gerrit Kuehn:
I grabed the CVS and it complained so I gave up
Sean, -v /please/.
"My car is broken" is a rather unspecific description of a
problem. The mechanic doesn't know where to look then. So please
describe in one or two sentences how to reproduce the error and
post it here (or in fidosoft.husky). Otherwise there is no
chance to fix it.
ROTFL, if I could tell my mechanic what was wrong, I would fix it
and save money :)))))
Well, the needed aplibs are already in the fastlst project;
maybe that's a point to start from.
fastlst fails under SuSe 9.0 maybe because of gcc 3.3
fastlst works for me under FreeBSD with gcc 3.3; which version
of fastlst do you use and what's the problem with it?
The version on the Husky web site
Same version fails to compile here on Debian 3.0r0, must remember
to try it on SuSE 8.0, so does fidoconfig and MsgEd gcc 2.95.4.
I tried CVS and that was worse :)
fastlst works for me under FreeBSD with gcc 3.3; which version
of fastlst do you use and what's the problem with it?
The version on the Husky web site
Same version fails to compile here on Debian 3.0r0, must remember
to try it on SuSE 8.0, so does fidoconfig and MsgEd gcc 2.95.4.
I tried CVS and that was worse :)
I pulled the entire cvs, ie. instead of "/cvsroot/husky co
smapi", I did a
"/cvsroot/husky co ."
Must check if I can determine if that includes unstable / current.
fastlst works for me under FreeBSD with gcc 3.3; which
version of fastlst do you use and what's the problem with it?
The version on the Husky web site
Same version fails to compile here on Debian 3.0r0, must
remember to try it on SuSE 8.0, so does fidoconfig and MsgEd
gcc 2.95.4.
I tried CVS and that was worse :)
I pulled the entire cvs, ie. instead of "/cvsroot/husky co
smapi", I did a
"/cvsroot/husky co ."
Must check if I can determine if that includes unstable /
current.
I think it is a gcc problem but not sure, I posted a messge somewhere about it :)
I think it is a gcc problem but not sure, I posted a messge somewhere
about it :)
Well, I did not see that post, might have missed it, why do you
think it is a gcc problem?
I grabed the CVS and it complained so I gave up
Sean, -v /please/.
Here goers, downloaded fastlst-203 from the SF Husky site and
configured okay and tried to make:
sean@home:/usr/src/fastlst-2.0.3> make
Hello sean.
02 Dec 03 10:53, you wrote to me:
fastlst works for me under FreeBSD with gcc 3.3; which
version of fastlst do you use and what's the problem with
it?
The version on the Husky web site
Same version fails to compile here on Debian 3.0r0, must
remember to try it on SuSE 8.0, so does fidoconfig and MsgEd
gcc 2.95.4.
I tried CVS and that was worse :)
I pulled the entire cvs, ie. instead of "/cvsroot/husky co
smapi", I did a
"/cvsroot/husky co ."
Must check if I can determine if that includes unstable /
current.
I think it is a gcc problem but not sure, I posted a messge
somewhere about it :)
Well, I did not see that post, might have missed it, why do you think
Hello Sean!
30 Nov 03 13:05, Sean Rima wrote to Gerrit Kuehn:
I grabed the CVS and it complained so I gave up
Sean, -v /please/.
Here goers, downloaded fastlst-203 from the SF Husky site and
configured okay and tried to make:
sean@home:/usr/src/fastlst-2.0.3> make
-bash-2.05b$ less README
Tobias Ernst:
Husky users: Do ***NOT*** run configure in the main directory of
this distribution. Change into the "makefls" subdirectory and run
"gmake all install" there without having run configure before
For technical reasons, for this package the "Husky" makefile is in
the "makefls" subdirectory instead of in the main directory.
For technical reasons, for this package the "Husky" makefile is in
the "makefls" subdirectory instead of in the main directory.
There is no makeflsdirectory in any ersion of fastlst that I have downloaded :)
Hello sean!
05 Dec 03 12:26, sean rima wrote to Gerrit Kuehn:
For technical reasons, for this package the "Husky" makefile is in
the "makefls" subdirectory instead of in the main directory.
There is no makeflsdirectory in any ersion of fastlst that I have
downloaded :)
This is next to impossible if you downloaded a recent source from SourceForge. Can you tell me
a) which command you used for cvs checkout, and
b) what the newest entry in your ChangeLog file is?
This is next to impossible if you downloaded a recent source from
SourceForge. Can you tell me
a) which command you used for cvs checkout, and
b) what the newest entry in your ChangeLog file is?
I read this and went and checked and yes I did download from SF *but*
the link is to the old site.
I grabbed the cvs and and currently am
grabbing huslylib etc to compile it
Hello sean!
06 Dec 03 21:35, sean rima wrote to Gerrit Kuehn:
This is next to impossible if you downloaded a recent source from
SourceForge. Can you tell me
a) which command you used for cvs checkout, and
b) what the newest entry in your ChangeLog file is?
I read this and went and checked and yes I did download from SF *but*
the link is to the old site.
This is what I meant with "some outdated links etc" in one of my
previous messages. I promise that I will update the pages as soon
as I have some time to spare for this. That's also the reason why I
keep asking about which sourcecode you /exactly/ use. :)
I grabbed the cvs and and currently am
grabbing huslylib etc to compile it
This is what I meant with "some outdated links etc" in one of my
previous messages. I promise that I will update the pages as soon
as I have some time to spare for this. That's also the reason why I
keep asking about which sourcecode you /exactly/ use. :)
And after much cvs updating I grenerated a executabke file :)
I think it is a gcc problem but not sure, I posted a messge
somewhere about it :)
Well, I did not see that post, might have missed it, why do you
think it is a gcc problem?
because with gcc 3.3.3 or whatever it is, it is very compilant whereas
it wasn't before. I am trying to track down that old message about fastlst.
fastlst works for me under FreeBSD with gcc 3.3; which
version of fastlst do you use and what's the problem with
it?
The version on the Husky web site
Same version fails to compile here on Debian 3.0r0, must
remember to try it on SuSE 8.0, so does fidoconfig and MsgEd
gcc 2.95.4.
I tried CVS and that was worse :)
I pulled the entire cvs, ie. instead of "/cvsroot/husky co
smapi", I did a
"/cvsroot/husky co ."
Must check if I can determine if that includes unstable /
current.
I think it is a gcc problem but not sure, I posted a messge
somewhere about it :)
Well, I did not see that post, might have missed it, why do you
think
Check that you really have smpapi-1.6.4-stable installed. Fastlst will
not compile with late, more recent versions of smpapi. Then the
procedure as below is:
make distclean (this will remove old stuff created during failed
compiles) ./configure
make
make install
make clean
That should do it for most 'nixes
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,024 |
| Nodes: | 17 (1 / 16) |
| Uptime: | 00:09:51 |
| Calls: | 503,341 |
| Calls today: | 10 |
| Files: | 107,032 |
| D/L today: |
28,816 files (1,976M bytes) |
| Messages: | 441,538 |
| Posted today: | 4 |