#1 generation of config.mk on suse 10.0

open
nobody
None
5
2013-01-24
2006-12-14
DerSchwabe
No

Hello,
I tried to compile, link and run the tcl-fortran interface on suse 10.0. To do this I had to do some changes in the config.tcl which generates config.mk which in turn is used in some makefiles. Suse 10.0 has tcl/tk version 8.4 installed.
1. Had to change the platform name from linux to unix in the script, since that is what I get from tcl.
2. Added -DG95 in the compiler_details for gcc for unix.
3. Changed the include path for unix g95 and gcc to -I../../src .
4. Added in compiler_details the --no-second-underscore option for g95.
5. Changed the library name for unix to libftcl.a in linker_details for ftcl_lib.
6. To compile preferentially with g95 changed the order in the fcompilers-list (that's a matter of taste) - no bug! Just for a complete description of the differences.
7. Commented out the 'set params(env) "cygwin"'-statement in proc findEnv {} because it persistenly set platform to cygwin.
8. Added the detection of shared object libraries in proc findTcl {}. Suse 10.0 just does not provide the static libraries, even not in the development package. So, instead of generating them by myself, I used this and it worked.
9. Added a 'set params(ldflags) linker_details() to include the "--no-second-underscore"-flag for the linking process.
I hope I got it complete and that it helps.
Best regards,
Joachim

Discussion

  • DerSchwabe
    DerSchwabe
    2006-12-14

    generated with diff -c config.tcl config_mod.tcl

     
    Attachments
  • Arjen Markus
    Arjen Markus
    2006-12-21

    Logged In: YES
    user_id=400048
    Originator: NO

    The config.tcl script is not very well tested. Distinguishing between Cygwin and MinGW under Windows turned out to be rather, uhm, interesting.

    As I have no access to Suse, I could not test it on that platform, but your description seems detailed enough to work the changes into the "official" version.

    Thanks for reporting this.