- Gfortran Mac Os
- Gfortran For Macos Mojave
- Mac Os Install Gfortran
- Gfortran Mac Download
- Gfortran Mac Os X
Tested on Linux and Mac, static and shared lib, namespaced and non-namespaced headers, but really only to the extent that it works for Psi4; all the fancy libtool options and Fortran interface not tested; test suite executed after build via ctest. But it has always totally passed or totally failed, which doesn’t inspire confidence. R for Mac OS X FAQ Frequently Asked Questions on R for Mac OS X Version 4.0.4 2021-02-15, R.app 1.74 Stefano M. Iacus Simon Urbanek Rob J.
GDB: The GNU Project Debugger
What is GDB?
GDB, the GNU Project debugger, allows you to see what is going on`inside' another program while it executes -- or what another programwas doing at the moment it crashed.
GDB can do four main kinds of things (plus other things in supportof these) to help you catch bugs in the act:
- Start your program, specifying anything that might affect its behavior.
- Make your program stop on specified conditions.
- Examine what has happened, when your program has stopped.
- Change things in your program, so you can experiment withcorrecting the effects of one bug and go on to learn about another.
What Languages does GDB Support?
GDB supports the following languages (in alphabetical order):- Ada
- Assembly
- C
- C++
- D
- Fortran
- Go
- Objective-C
- OpenCL
- Modula-2
- Pascal
- Rust
GDB version 10.1
Gfortran Mac Os
Version 10.1 of GDB, the GNUDebugger, is now available for download. See the ANNOUNCEMENT for detailsincluding changes in this release.An errata list (PROBLEMS) and documentationare also available.
News
The latest version of GDB, version 10.1, is available for download.
This version of GDB includes the following changes and enhancements:
- Support for debugging new targets:
- BPF (bpf-unknown-none)
- GDBserver support for the following targets:
- ARC GNU/Linux
- RISC-V GNU/Linux
- Multi-target debugging support (experimental)
- Support for debuginfod, an HTTP server for distributing ELF/DWARF debugging information as well as source code.
- Support for debugging a 32-bit Windows program using a 64-bit Windows GDB.
- Support for building GDB with GNU Guile 3.0 and 2.2 (in addition to 2.0)
- Improved performance during startup through the use of threading during symbol table loading (an optional feature in GDB 9, now enabled by default in GDB 10).
- Various enhancements to the Python and Guile APIs
- Various TUI Mode fixes and enhancements.
- Other miscellaneous enhancements:
- Detection when attaching to a process of a mismatch between this process and the executable previously loaded into GDB.
- Support for default arguments for 'alias' commands.
- GDBserver support for the following host triplets has been removed:
- i[34567]86-*-lynxos*
- powerpc-*-lynxos*
- i[34567]86-*-nto*
- bfin-*-*linux*
- crisv32-*-linux*
- cris-*-linux*
- m32r*-*-linux*
- tilegx-*-linux*
- arm*-*-mingw32ce*
- i[34567]86-*-mingw32ce*
The GDB 10 branch (gdb-10-branch) has been created.To check out a copy of the branch use:
The latest version of GDB, version 9.2, is available for download.
This is a minor corrective release over GDB 9.1, fixing the followingissues:
- PR tui/25586 (Resizing the source/disassembly or command window produces corrupted display)
- PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior address)
- PR build/25981 (Use of short i386 register names breaks compilation on recent Solaris 11.4)
- PR symtab/26003 (infinite loop loading symbols from separate debug objfile)
- PR build/26029 (GDB build failure on SPARC)
The GDB maintainers are looking for contributors interestedin reversible debugging.
Late breaking information, such as recently added features, can befound in the NEWS file in the gdb source tree. Old announcements are in thenews archive.Please send FSF & GNU inquiries & questions to gnu@gnu.org. There are also other ways tocontact the FSF.
This page is maintained by the GDBdevelopers.
Copyright Free Software Foundation, Inc., 51 Franklin St - FifthFloor, Boston, MA 02110-1301 USA.
Verbatim copying and distribution of this entire article ispermitted in any medium, provided this notice is preserved.
Last modified 2020-10-24.
Gfortran For Macos Mojave
If you are installing the library directly from the sources, the recommended way to do so is by using GNU Autotools.
To install the library, just use the standard procedure:
Do not forget to replace PATH/TO/LIBXC
by the some appropriate path on your file system and make sure that you have write permissions.
If you obtained the sources directly from the git repository, you will first need to generate configure
by running
Support for building the sources using CMake has also been recently contributed by Lori Burns.
The CMake file has the following caveats
- tested on Linux and Mac, static and shared lib, namespaced and non-namespaced headers, but really only to the extent that it works for Psi4
- all the fancy libtool options and Fortran interface not tested
- test suite executed after build via
ctest
. But it has always totally passed or totally failed, which doesn’t inspire confidence - The generated
libxc_docs.txt
is large, and the generation step sometimes balks on it, leading toxc_funcs.h
not found errors. Just execute again.
Building with CMake
Mac Os Install Gfortran
Use the following procedure:
The build is also responsive to
- static/shared toggle
BUILD_SHARED_LIBS
- install location
CMAKE_INSTALL_PREFIX
- namespacing of headers
NAMESPACE_INSTALL_INCLUDEDIR
- of course,
CMAKE_C_COMPILER
,BUILD_TESTING
, andCMAKE_C_FLAGS
See CMakeLists.txt for options details. All these build options should be passed as cmake -DOPTION
.
Detecting with CMake
CMake builds install with LibxcConfig.cmake
, LibxcConfigVersion.cmake
, and LibxcTargets.cmake
files suitable for use with CMake find_package()
in CONFIG
mode.
find_package(Libxc)
- find any xc libraries and headersfind_package(Libxc 3.0.0 EXACT CONFIG REQUIRED COMPONENTS static)
- find Libxc exactly version 3.0.0 built with static libraries or die trying
See cmake/LibxcConfig.cmake.in for details of how to detect the Config file and what CMake variables and targets are exported to your project.
Use with CMake
After find_package(Libxc ...)
,
- test if package found with
if(${Libxc_FOUND})
orif(TARGET Libxc::xc)
- link to library (establishes dependency), including header and definitions configuration with
target_link_libraries(mytarget Libxc::xc)
- include header files using
target_include_directories(mytarget PRIVATE $<TARGET_PROPERTY:Libxc::xc,INTERFACE_INCLUDE_DIRECTORIES>)
- compile target applying
-DUSING_Libxc
definition usingtarget_compile_definitions(mytarget PRIVATE $<TARGET_PROPERTY:Libxc::xc,INTERFACE_COMPILE_DEFINITIONS>)
Python Library
Optional Python bindings are available through the cytpes module. To installinto Python site-packages plese run:
or, to install locally for development:
The Python bindings require the CMake compilation pathway and the PythonNumerical Python library. A short usage example is provided below:
Libxc is now available in Fedora. To compile against Libxc one just needs to install the development package with
If the Libxc Fortran module file is needed, one needs to add ‘-I/usr/lib64/gfortran/modules’ or ‘-I/usr/lib/gfortran/modules’ (on 32-bit systems) to the compiler arguments.
Libxc was added to this Ubuntu repository for easier installation. To add this repository to Ubuntu, all one has to do is type-in:
Now Libxc can be installed via the Ubuntu software centre and will receive automatic updates.
Libxc for Mac OSX is available from the Homebrew package manager. After Homebrew installation one types in:
Libxc was also added to the macports repository for easier installation on Mac OS X. After installing macports the user can type in:
Gfortran Mac Download
Gfortran Mac Os X
Again the user will receive automatic updates. Note: installation time takes very long because gfortran needs to be built first.