-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
starlink build on debian 12 #82
Comments
Hi Paul, looks like the 2023A release is just on a branch, so you should check that out. Re: the tkimg issue. This is one that has been reported before: https://www.jiscmail.ac.uk/cgi-bin/wa-jisc.exe?A2=ind2307&L=STARLINK&O=D&P=50 The solution there was to remove some of the system libraries that are interfering with the Re: VTK, that also sounds good, compilers like to get more fussy so these sorts of issues turn up Cheers, |
Tags have been added for 2023A. |
We actually had issues building VTK on macOS for this build. In the end we turned it off for the release (which I just realised got missed from the release notes and have added back in). VTK is I believe only used for the Gaia 3D rendering, so everything else should work fine if there are any issues, but that's where to check if you want to see if your changes worked. You can also turn off VTK in the configure step. I'm hoping I'll get a chance to try updating VTK and see if that solves our build issues without breaking Gaia.
I'd love to get the changes you made and the latex/package versions you were using please. |
Thank you all for your responses. For vtk with gaia, is the 3d rendering for dealing with fits data cube files? If yes, I've done some testing with those types of files and everything works fine. Sarah - for docs building the debian 12 dpkg is texlive version 2022.20230122-3
I have to add these 2x lines...
to the top of these tex files for make world to continue... some further oddments...
Since my original post, something that I have noticed is that the html docs have not been created at all for any docs, so the findme and showme commands produce nothing. All of the pdf's are created fine: I'm presuming that I should still see html docs and that star2html creates these?
but there is no html file - it's the same for everything else as well. To test further, I've copied sun214.tex from the source folder to a temp folder and ran "star2html sun214.tex" but get this...
The sun214.htx directory is created: the final line of sun214.htx/sun214.log shows... Best regards |
Hi all
Prelim query: I normally build starlink from the github source for our debian amd64 systems - is the new starlink 2023A release taken from the github source on a specific date or commit as I cannot find a release or tag for 2023A?
Main query: I've cloned the latest github source on 09 Jan 2024, and on debian 12 amd64, make world fails at thirdparty/tclsys/tkimg with...
It looks like that is for "JBIG Compression Algorithm Support". By using "--disable-jbig" as a configure option within the libtiff source and starting from a newly cloned source, I can successfully build that part.
Does anyone know if doing this cause any future usage problems though? After I got everything installed, everything has worked so far with some limited testing.
make world also fails at thirdparty/kitware/vtk with a few errors such as...
which I've gotten around by adding an extra "const" term to...
thirdparty/kitware/vtk/cmake/Source/CTest/cmCTestBuildHandler.cxx
line 575 to be...
bool operator()(std::string const& l, std::string const& r) const
thirdparty/kitware/vtk/VTK/Rendering/Label/vtkLabelHierarchyPrivate.h
line 77 to be...
bool operator () ( const vtkIdType& a, const vtkIdType& b ) const
thirdparty/kitware/vtk/VTK/Rendering/Label/vtkLabelHierarchy.cxx
line 528 to be...
const vtkHierarchyNode & b) const
I've also had to tweak a few of the doc .tex files to include hyperref and html packages so that they can build correctly - I can provide more details on those if anyone is interested.
After doing those changes, everything builds correctly: no problems at all with the starjava build afterwards.
So am I doing the right things here?
Best regards
Paul
The text was updated successfully, but these errors were encountered: