Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (49 - 51 of 122)

Ticket Resolution Summary Owner Reporter
#67 fixed Running configure without g++ => cryptic error andreasw plb
Description

While setting up bcp (with CoinUtils?? 2.2.5), I ran into the following problem :

configure: error: Cannot find integer type with 64 bits configure: error: /bin/bash '../../CoinUtils?/configure' failed for CoinUtils?

I'm enclosing config.log.

I tried several times. I had gcc installed, but not g++. I set up g++ and ran configure, and it went just fine. I'm enclosing the config.log of the successful run. If the failure was indeed caused by the absence of g++, it might be useful to make the error message more specific.

#68 fixed User-given FFLAGS ignored for dlamch compilation andreasw andreasw
Description

Hi Stefan :-)

The compilation of dlamch still has some problems. For example, if someone sets FFLAGS, this is completely ignored when compiling it. (In an IBM context, someone had -fPIC included in FFLAGS and uses --disable-shared, so this doesn't work when you later try to make a shared library)

Instead of setting it to the coin_warn_flags etc, would it make more sense to scan the content of FFLAGS and remove anything of the form '-O*' and replace it by '-O0'? Not sure if that works for all compilers though (Windoofs?). At the very least, we should make DLAMCH_FFLAGS an argument that one can set.

What do you think?

Andreas

#69 fixed HSL ThirdParty build system in IpOpt out of date andreasw jhogg
Description

STFC now distribute codes and their dependencies in separate files. For example let us consider MA57, observing that no naming scheme is given when downloading the file (it just appears as text in the browser).

We have wlog two files: ma57d.f ma57d.deps.f

The current build system expects a single file ma57ad.f. This models how things used to be done - since these scripts were written it seems that renaming and management practice changes have occurred.

Obviously in this case [and for all F77 codes] we can trivially work around this by concatenating and renaming the result ma57ad.f.

I am currently in the process of adding an interface to HSL_MA77 which is a Fortran 90 code. As a result we have three files: hsl_ma77d.f90 hsl_ma77d.deps.f90 hsl_ma77d.deps.f

We have dependencies in both fixed and free source formats, so concatenating these files will produce compile errors. Further we need to add a dependency to ensure that the f90 deps are compiled before the f90 code so the module files are readable.

We should also endeavor to ensure the f77 and f90 compilers used are compatible - I've seen some nasty messes with automake choosing g77 (GNU) and f95 (NAG) compilers which don't produce stuff one can easily link together due to underscoring practices. I neat solution might be to default to using the F95 ($FC) compiler to compile F77 code in place of the ($F77) compiler.

I don't have the necessary knowledge of automake and the IpOpt? build system to easily make these changes myself however.

Jonathan Hogg

Note: See TracQuery for help on using queries.