After successfull emerging sather-1.3.ebuild (I had to extend the patch, which I will include with the bugreport) I couldn't compile sather programs (sacomp), with the error report: "cannot open configuration file /usr/sather/system/CONFIG for reading" Reproducible: Always Steps to Reproduce: 1. emerge 2. write the helloworld proggie 3. sacomp -main HELLO_WORLD -o hw hw.sa Actual Results: sacomp stopped compilation Expected Results: sacomp shoud've compiled the source file Here is a diff for patching the ebuild file. The error was due to an incorrect path. diff -ru sather-1.3.ebuild.orig sather-1.3.ebuild --- sather-1.3.ebuild.orig 2005-01-24 23:57:29.837003984 +0100 +++ sather-1.3.ebuild 2005-01-24 23:58:21.050218392 +0100 @@ -61,8 +61,8 @@ rm -rf ${D}/usr/${PN}/sacomp-boot rm -rf ${D}/usr/${PN}/system dodir /usr/${PN}/system - cp ${WORKDIR}/${PN}-1.3/system/CONFIG ${D}/usr/${PN}/system - cp ${WORKDIR}/${PN}-1.3/system/FORBID ${D}/usr/${PN}/system + cp ${WORKDIR}/${MY_P}/system/CONFIG ${D}/usr/${PN}/system + cp ${WORKDIR}/${MY_P}/system/FORBID ${D}/usr/${PN}/system cd ${WORKDIR} dodoc doc/${PN}-specification-000328.ps.gz doc/${PN}-tutorial-000328.ps.gz doc/satish-thatte.ps.gz doc/Descript.ps.gz
Created attachment 49419 [details] ebuild fixes This ebuild fixes my bug :p It should probably be renamed sather-1.3-r1.ebuild
Created attachment 49420 [details, diff] patch for sather with regard to gcc3xx This patch is required in order to be able to compile the sather sources with gcc3xx
So I included the patch to make the sources compile with gcc3xx compilers. The problem was due to the misuse of macro's. Since gcc3xx the rules are more strict with regard to calling functions. Though, it is easily fixed. This should get the ebuild unmasked for x86 keyword. grtz Tijs
the patch appears to be binary. Reattach as text/plain please.
the patch is .gz file
Created attachment 51863 [details, diff] patch plain text
This ebuild/patch make the sources compile again with gcc3xx. Though, I've experienced some segfaults while using sather. I don't know the cause yet, I don't have the time right now. But it appears to be while using strings in classes. The bugfix could be causing these segfaults... grtz
Created attachment 63475 [details] an ebuild for last version Attaching an ebuild for the latest "stable" release, dated 2005-06. According to website the 1.3 branch is for betas (apparently they used stale Linux kernel convention) and is antiquated at this moment. Last 1.3_beta release dates 2000! Therefore I would suggest that all development on this package concentrates around the latest releases *by date*, which are stable releases at this point. I tried to adjust the build process to match the new code (there is no configure anymore, just a plain Makefile. Plus I had to strip some env vars which no longer corresponded to reality). Also I adjusted src_install to use SATHER_DEST var, for ease of location changes and pointed that over to /usr/lib/${PN} to comply at least somewhat with FHS. Also, the ${My_P} was no longer necessary. See also next comment.
Then I get to testing this thing and realised that this package bootstraps itself and only has x86 compiler included for bootstrapping. Since I do not have a working x86 chroot at the moment (only amd64) I will release this bug to bug-wranglers, in the hope that somebody might pick it up. bug-wranglers: if assignment of this bug is problematic (I would have suggested lang-misc herd, but its not really functional yet - I don't think there is anybody on it except me, despite my calls :( ), I'd suggest closing it with LATER. You may even reassign it to me upon such closure, or just bounce back and I'll close it with LATER myself. Tijs Van: Looks like sather is under large revamp right now, so I wouldn't expect its developers to produce binaries for many arches as of yet. However if you have an idea on how this can be compiled under amd64 please feel free to reopen the bug on me. That, or try bugging me a month or two later (Hopefully but then I'll get an external HDD and will have x86 chroot running). I am settling in a new place and becoming more active again, but I have quite a bit of stuff to take care off yet, and this package is not very high priority. Of course any fixing/testing on your side is appreciated ;). George
@george - is upstream still alive? Also, this is some mysterious version in portage, I couldn't find 1.3 anywhere or their site??? Probably should be removed from portage otherwise, as it doesn't compile w/ any usable gcc version as it is.
old
Punted as of now!
