# Building mrtrix3 on RHEL 7 **URL:** \ **Category:** Uncategorized\ **Tags:** installation\ **Created:** [March 29, 2018, 6:35pm UTC](https://community.mrtrix.org/t/building-mrtrix3-on-rhel-7/1558 "2018-03-29T18:35:10Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![jdtournier](https://community.mrtrix.org/user_avatar/community.mrtrix.org/jdtournier/32/2594_2.png) [@jdtournier](https://community.mrtrix.org/u/jdtournier)\ **Post date:** [April 3, 2018, 10:38am UTC](https://community.mrtrix.org/t/building-mrtrix3-on-rhel-7/1558/8 "2018-04-03T10:38:30Z")
Yes, that’s more or less the approach I’d suggested in [the thread I mentioned earlier](http://community.mrtrix.org/t/installation-problem-json-requirements-windows/1512/20) – although I would insert a symbolic link to the library, rather than a full copy: > [@Installation Problem, JSON requirements | Windows](https://community.mrtrix.org/t/installation-problem-json-requirements-windows/1512/21): > > I think your best bet will be to create a symbolic link to the right library in the MRtrix3 lib/ folder – our executables are hard-coded to look there first, to make sure they find the right version of the MRtrix3 library (libmrtix-3.0\_RC2.so or similar), which means that any libraries placed here will be used in preference to the system ones – but only for our executables, just what we want… Glad to hear it’s now working! --- _[View the full topic](https://community.mrtrix.org/t/building-mrtrix3-on-rhel-7/1558)._