Ticket #28154 (closed update: fixed)
check-in request: octave-devel 3.3.90 revision
| Reported by: | lukas.reichlin@… | Owned by: | michaelld@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | octave-devel |
Description
I updated the octave-devel Portfile to revision 1. The file is attached to this ticket.
The README.MacOS thread (and other Mac-related ones) on
https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2011-January/thread.html
might be of interest.
Lukas
Attachments
Change History
Changed 2 years ago by lukas.reichlin@…
- Attachment Portfile_2011_01_25_2312 added
Changed 2 years ago by lukas.reichlin@…
Portfile Patch 3.3.90_0 ---> 3.3.90_1
comment:1 Changed 2 years ago by macsforever2000@…
- Cc michaelld removed
- Owner changed from macports-tickets@… to michaelld@…
- Version 1.9.2 deleted
- Type changed from submission to update
Trac requires complete email addresses.
comment:2 Changed 2 years ago by michaelld@…
Can you please summarize why these changes are necessary and what they do? Yes, I've read through the supporting bug ticket & other documents, but I'd appreciate knowing what these changes do with whatever brevity you can afford.
comment:3 Changed 2 years ago by lukas.reichlin@…
3.3.90_0 has 52 failing tests, 3.3.90_1 only 2. See README.MacOS post from Jarno.
comment:4 Changed 2 years ago by michaelld@…
- Status changed from new to closed
- Resolution set to fixed
Fixed in r75513. I also cleaned up the Portfile a bit. AFAICT, adding "FDFLAGS=.../libstdc++..." just adds that library to that linked with the 'octave' executable. This library is already referenced from the Octave libraries (${prefix}/lib/octave/lib*), which are in turn referenced by both ${prefix}/bin/octave as well as the various SO's in ${prefix}/libexec/octave/3.3.90/oct/x86_64-apple-darwin10.6.0/ ... So, if adding in this flag somehow works "better" than without then I'm all for using it. But I don't understand how it helps. That said, I also haven't tried the various instructions you provide in the octave bug ticket -- so I'll just take your word that it help ;)


octave-devel @3.3.90_1