Jai Dayal wrote:
> How about I do cmake instead of autoconf? That way, in theory, one
> should be able to do the whole thing regardless if it's windows,
> linux, or unix... given that they have cmake installed, of course.
>
> Any objections?
fine with me
-
How about I do cmake instead of autoconf? That way, in theory, one should
be able to do the whole thing regardless if it's windows, linux, or unix...
given that they have cmake installed, of course.
Any objections?
Jai
On Wed, Oct 16, 2013 at 6:06 PM, Ben St-Pierre wrote:
> Dear Jai,
>
> I rep
Dear Jai,
I repeatedly asked you to scratch your own itch. I also asked you if some
search results would have helped. Both fail to qualify as pretending to
know how to solve your problem.
Do you think that "please download the latest sources" count as a "please
restart your computer" for newly
>Because it's not my script.
>Because it's not 100% broken.
You pretended to know what to do to fix it, thus, you are not responsible
for all failed solutions that you bring up. You introduced many failed
solutions.
>That your claim not to have flamed can easily be proven false and that
newly mi
> How do I donate ?
We (Fulvio) do (does) not accept donations. There's some Kickstarter idea
that would need to be developed. But nothing is certain on that front.
Wikipedia always needs money.
I'm sure Fulvio would appreciate if you'd work on creating an Autoconf'ed
configuration instead of d
> Why can't you just admit that your little script is 100% broken?
Because it's not my script.
Because it's not 100% broken.
Because the admission is already in the comment of makefile.conf
Because the admission is implied in the many requests you ignored to
scratch your own itch and produce so
Brilliant. That worked. How do I donate to scid?
On Wed, Oct 16, 2013 at 5:04 PM, f...@libero.it wrote:
> >> Yes, I am using LinuxMint, an Ubuntu derivative, but not Ubuntu. You
> are right, it's good to clarify that.
>
> Ok, I git blamed the configure file and "/usr/lib/x86_64-linux-gnu" is
>
>> Yes, I am using LinuxMint, an Ubuntu derivative, but not Ubuntu. You are
>> right, it's good to clarify that.
Ok, I git blamed the configure file and "/usr/lib/x86_64-linux-gnu" is founded
automatically from 01-may-2013.Please try to download the latest code: go to
http://sourceforge.net/p/s
Yes, I am using LinuxMint, an Ubuntu derivative, but not Ubuntu. You are
right, it's good to clarify that.
Okay, so then install tcl/tk in a separate directory, remove your existing
ones, and then try to have scid compile with the new build?
I installed tcl/tk using Mint's package manager. It doe
It works for me, so it's not *100%* broken, surely...
And I'm pretty sure your very first message indicated that you *are* using
Ubuntu (or at least something so heavily Ubuntu-derived that the kernel
name still has 'Ubuntu' in it).
On Wed, Oct 16, 2013 at 8:52 PM, Jai Dayal wrote:
> "
> - Ya'
"
- Ya'll have no idea how to use autotools [the title];
- Do you people not know how to actually use autotools to avoid this from
happening? Seriously, this isn't advanced stuff.
- Your makefile is completely inconsistent.
- Wow. you all have *no idea* how to write a makefile
- This is ridiculous.
>
> I'm stating a fact:
Many facts, in fact:
- Ya'll have no idea how to use autotools [the title];
- Do you people not know how to actually use autotools to avoid this from
happening? Seriously, this isn't advanced stuff.
- Your makefile is completely inconsistent.
- Wow. you all have *no idea*
I'm not flaming anyone. I'm stating a fact: this configure platform you all
are using is broken.
It allows to specify the location of tcl/tk. I've done that; both using
variables passed in, and by manually editing the makefile itself. Neither
of these solutions have worked, so now you require edit
Thank you, Jai Dayal.
Now, how would any competent programmer presumably like you would solve
this problem?
More precisely, here's the relevant bit from the makefile.conf:
# TCL_INCLUDE, TCL_LIBRARY, TK_LIBRARY: these are the compiler options
#needed for linking Scid with Tcl/Tk. The progra
No.
On Wed, Oct 16, 2013 at 2:41 PM, Ben St-Pierre wrote:
> Does
>
> > TCL_LIBRARY = -L/usr/lib/x86_64-linux-gnu -ltcl8.5
>
> work for you, Jayal?
>
> A simple yes or no would suffice.
>
>
>
> --
> October Webinars: Cod
Does
> TCL_LIBRARY = -L/usr/lib/x86_64-linux-gnu -ltcl8.5
work for you, Jayal?
A simple yes or no would suffice.
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performan
>>I know in your world, simple "restart the computer" solutions work, but in
>>the real world, they rarely work.Oh, right! Have you tried to restart your
>>computer? :-)
>>Of course, this obvious solution has been tried. As usual, it does not work.
>>If you post your Makefile and the full gc
"Well, good for you. So have you solved with:
TCL_LIBRARY = -L/usr/lib/x86_64-linux-gnu -ltcl8.5"
I know in your world, simple "restart the computer" solutions work, but in
the real world, they rarely work.
Of course, this obvious solution has been tried. As usual, it does not
work.
On Wed, Oct
>>You have no idea about what you're talking.
Well, good for you. So have you solved with:
TCL_LIBRARY = -L/usr/lib/x86_64-linux-gnu -ltcl8.5
?
--
October Webinars: Code for Performance
Free Intel webinars can help you
Okay, so then don't call it "configure" if it's not a configure script
then; and don't accept the same variables, i.e., --prefix
"well, at least for that i think you should blame the inventors of c
(Thompson and Ritchie)"
No, that's not true, at all. Any competent programmer would know that if
yo
>>SO you're saying that the configure script is not the standard GNU autotools
>>offering, but something created independently?
Exactly. If you don't believe me you can simply open the configure file with a
text editor and see that it's a tcl script
>>Your makefile is completely inconsistent.
>
> Wow. you all have *no idea* how to write a makefile
>
Is that an offer to write one?
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI,
Rather than attack the authors of the makefile, just submit a patch to
improve it.
This is open source software, I'm sure they would welcome improvements to
make cross-platform builds better. I'm sure they'd be willing to return the
money you paid for this source code, as well. :P
And, in defense
SO you're saying that the configure script is not the standard GNU
autotools offering, but something created independently?
Your makefile is completely inconsistent.
For TCL_INCLUDE, you don't specify tcl.h
for TCL_LIBRARY, you have to specify the .a/.so file.
Wow. you all have *no idea* how to
>>Do you people not know how to actually use autotools to avoid this from
>>happening? Seriously, this isn't advanced stuff.
I'm not sure i fully understand your question, actually scid do not use
autotools.
>>How do I fix this?
the wrong part is "/usr/include/tcl8.5/tcl.h"manually edit
I get it to configure, and then type make only to get
g++ -O3 -fno-rtti -fno-exceptions -std=c++0x -pthread -Wall
/usr/include/tcl8.5/tcl.h -o src/pgnscid.o -c src/pgnscid.cpp
g++: fatal error: cannot specify -o with -c, -S or -E with multiple files
compilation terminated.
make: *** [src/pgnscid.
26 matches
Mail list logo
