### Author:  [@Haocheng\_Liu](https://discourse.paraview.org/u/Haocheng_Liu)
#### Post date: [November 18, 2019, 9:46pm UTC](https://discourse.paraview.org/t/paraview-master-build-error-related-to-libxml-osx-10-14/2997/1 "2019-11-18T21:46:10Z")
Hi ParaView developers,
I’m doing a clean build on osx 10.14 + CMake 3.15.0 and it fails due to libxml issue. Any ideas?
[CMakeCache.txt](https://discourse.paraview.org/uploads/short-url/kLo1GlvabC0aCEsIAB8yZcCnwnV.txt) (291.1 KB)
ParaView SHA:
```auto
commit 3cdf5c845e23437cf51dc3cd36c70f133917b67c (HEAD -> master, origin/master, origin/HEAD)
Merge: d6d55557c 3d322a119
Author: Utkarsh Ayachit
Date: Mon Nov 18 16:49:05 2019 +0000
```
> - error message:
> /Users/haochengliu/Kitware/cmb/buildDebug-cmb6-qt5.12/superbuild/paraview/src/VTK/ThirdParty/libxml2/vtklibxml2/libxml.h:85:71: error: expected function body after function declarator
> void \_\_xmlLoaderErr(void \*ctx, const char \*msg, const char \*filename) LIBXML\_ATTR\_FORMAT(2,0);
> ^
> In file included from /Users/haochengliu/Kitware/cmb/buildDebug-cmb6-qt5.12/superbuild/paraview/src/VTK/ThirdParty/libxml2/vtklibxml2/HTMLparser.c:47:
> /Users/haochengliu/Kitware/cmb/buildDebug-cmb6-qt5.12/superbuild/paraview/src/VTK/ThirdParty/libxml2/vtklibxml2/buf.h:22:1: error: unknown type name ‘xmlBufPtr’
> xmlBufPtr xmlBufCreate(void);
> ^
> /Users/haochengliu/Kitware/cmb/buildDebug-cmb6-qt5.12/superbuild/paraview/src/VTK/ThirdParty/libxml2/vtklibxml2/buf.h:23:1: error: unknown type name ‘xmlBufPtr’
> xmlBufPtr xmlBufCreateSize(size\_t size);
> ^
> /Users/haochengliu/Kitware/cmb/buildDebug-cmb6-qt5.12/superbuild/paraview/src/VTK/ThirdParty/libxml2/vtklibxml2/buf.h:24:1: error: unknown type name ‘xmlBufPtr’
> xmlBufPtr xmlBufCreateStatic(void \*mem, size\_t size);
> ^
---
### Author:  [@Haocheng\_Liu](https://discourse.paraview.org/u/Haocheng_Liu)
#### Post date: [November 19, 2019, 4:45pm UTC](https://discourse.paraview.org/t/paraview-master-build-error-related-to-libxml-osx-10-14/2997/2 "2019-11-19T16:45:21Z")
Close since it’s a local system setting error.
---
### Author:  [@David\_Duke](https://discourse.paraview.org/u/David_Duke)
#### Post date: [June 26, 2020, 10:48am UTC](https://discourse.paraview.org/t/paraview-master-build-error-related-to-libxml-osx-10-14/2997/3 "2020-06-26T10:48:28Z")
Could you provide any further information on the nature of the error, i.e. what setting was incorrect;
I am having the same problem in building VTK.
thanks - David.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 26, 2020, 4:26pm UTC](https://discourse.paraview.org/t/paraview-master-build-error-related-to-libxml-osx-10-14/2997/4 "2020-06-26T16:26:56Z")
Welcome to ParaView, David. Are you building from a clean build directory? If not, I recommend cleaning your build directory and trying again, particularly if you have updated your VTK source and are rebuilding in an old build directory.
---
### Author:  [@David\_Duke](https://discourse.paraview.org/u/David_Duke)
#### Post date: [June 27, 2020, 11:41am UTC](https://discourse.paraview.org/t/paraview-master-build-error-related-to-libxml-osx-10-14/2997/5 "2020-06-27T11:41:12Z")
Hi Cory. I did a fresh VTK source checkout from github and then a clean build.
On linux it ran fine. on OSX I hit the problem. Whilst I have a built version now on linux
for pragmatic reasons I prefer to work on my Mac so any solution would be helpful.
thanks
David
---
### Author:  [@David\_Duke](https://discourse.paraview.org/u/David_Duke)
#### Post date: [July 1, 2020, 8:02pm UTC](https://discourse.paraview.org/t/paraview-master-build-error-related-to-libxml-osx-10-14/2997/6 "2020-07-01T20:02:09Z")
I did a further fresh checkout and build sucessfully on OSX so issue resolved. Unclear what happened the first time, but seems to be working now.
thanks - David
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 1, 2020, 8:03pm UTC](https://discourse.paraview.org/t/paraview-master-build-error-related-to-libxml-osx-10-14/2997/7 "2020-07-01T20:03:14Z")
Thanks for the followup, David!