#2276 closed defect (fixed)
New gcc requires swig 1.3.33 for perl bindings
Reported by: | warmerdam | Owned by: | Mateusz Łoskot |
---|---|---|---|
Priority: | normal | Milestone: | 1.5.3 |
Component: | PerlBindings | Version: | 1.5.0 |
Severity: | normal | Keywords: | swig gcc build |
Cc: | Ari Jolma, martinl, Markus Neteler |
Description
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466785
Basically it seems we need to upgrade the packaging machine www.gdal.org/www.buildbot.org to have swig 1.3.33.
Change History (8)
comment:1 by , 16 years ago
Owner: | changed from | to
---|
comment:2 by , 16 years ago
I vaguely remember this bug, when I upgraded to perl 5.10 in Windows, it was easy to fix by upgrading swig. I have swig 1.3.33 in my main Linux machine (but perl is still 5.8.8) - it's been upgraded to that without any special attention. I had another issue with Perl 5.10, which I reported to Swig people: https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1904537&group_id=1645 and the fix is now in 1.3.35 - it's a quite minor issue and I'm not sure if it shows up in tests.
comment:3 by , 16 years ago
Status: | new → assigned |
---|
I would like to ask for final confirmation that I should proceed and upgrade SWIG from 1.3.31 to 1.3.33
comment:5 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I've upgraded SWIG to latest 1.3.36 on the xblade14-2 machine.
[mloskot@xblade14-2 src]$ swig -version SWIG Version 1.3.36 Compiled with g++ [i686-pc-linux-gnu] Please see http://www.swig.org for reporting bugs and further information
follow-up: 7 comment:6 by , 16 years ago
Cc: | added |
---|
Martin, will this SWIG update break the GRASS compilation cronjobs on xblade14-2?
Markus
PS: please remember that xblade14-2 is a multi-project machine: GDAL, GRASS, QGIS, ...
comment:7 by , 16 years ago
Replying to neteler:
Martin, will this SWIG update break the GRASS compilation cronjobs on xblade14-2?
no, it shouldn't break GRASS compilation, SWIG >= 1.3.31 should be OK (there was problem with the previous SWIG versions).
Martin
comment:8 by , 16 years ago
Marcus, Martin,
Thanks for pointing the potential risk. Please, notify me in case of any troubles with new SWIG version.
Actually, it's Mateusz who will need to upgrade the packaging machine -- reassigning. Ari, you might want to verify that SWIG 1.3.33 is fine.