From smr at sumost.ca Thu Oct 19 09:53:44 2006 From: smr at sumost.ca (Steve Robbins) Date: Thu, 19 Oct 2006 08:53:44 -0500 Subject: [MINC-development] Fwd: Bug#394071: Trouble using minc headers with gcc >= 4.0 Message-ID: <20061019085344.vy7mlew4uggsooos@sumost.ca> Hello MINC developers, The provided patch (for MINC 1) replaces use of "Status" by "VIO_Status" to avoid a compiler error building freesurfer. Does that appear to be a reasonable idea to you folks? If so, shall I attempt to commit it? Thanks, -Steve P.S. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394071 for the patch. ----- Forwarded message from michael.hanke at gmail.com ----- Date: Thu, 19 Oct 2006 10:37:12 +0200 From: Michael Hanke Reply-To: Michael Hanke , 394071 at bugs.debian.org Subject: Bug#394071: Trouble using minc headers with gcc >= 4.0 To: Debian Bug Tracking System Package: minc Severity: normal Tags: patch Hi, I'm packaging a software that depends on the minc library. Compiling the package I get an error when using gcc 4.0 or 4.1 (gcc 3.4 is fine): --------------------------- make[2]: Entering directory `/home/michael/freesurfer/freesurfer-dev3/unix' source='xvmri.c' object='xvmri.o' libtool=no \ depfile='.deps/xvmri.Po' tmpdepfile='.deps/xvmri.TPo' \ depmode=gcc3 \ /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/X11R6/include -I/usr/X11R6/include -I/usr/X11R6/include +-I../include -I../include/dicom -DLinux -DANSI -I/usr/include/core -I/usr/include/vcl -I/usr/include/v3p/netlib +-g -O2 -Wall -Werror -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/usr/include/vxl/vcl -I/usr/include/cxl/core +-I/usr/include/vxl/v3p/netlib -c `test -f 'xvmri.c' || echo './'`xvmri.c In file included from /usr/include/volume_io.h:40, from ../include/mri.h:20, from xvmri.c:21: /usr/include/volume_io/basic.h:161: error: two or more data types in declaration specifiers make[2]: *** [xvmri.o] Error 1 make[2]: Leaving directory `/home/michael/freesurfer/freesurfer-dev3/unix' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/michael/freesurfer/freesurfer-dev3' make: *** [all] Error 2 --------------------------- I contacted upstream about this issue and learned that they use a patched version of minc to address this problem. They kindly provided me with the patch (courtesy of Nick Schmansky). I'm not completely sure whether one could handle this situation without modifying minc, though. Please consider including this patch into the Debian package. Thanks, Michael -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (600, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- GPG key: 1024D/3144BE0F Michael Hanke http://apsy.gse.uni-magdeburg.de/hanke ICQ: 48230050 ----- End forwarded message ----- From smr at sumost.ca Thu Oct 19 10:17:31 2006 From: smr at sumost.ca (Steve Robbins) Date: Thu, 19 Oct 2006 09:17:31 -0500 Subject: [MINC-development] Fwd: Bug#394071: Trouble using minc headers with gcc >= 4.0 In-Reply-To: <20061019085344.vy7mlew4uggsooos@sumost.ca> References: <20061019085344.vy7mlew4uggsooos@sumost.ca> Message-ID: <20061019091731.tcj6krmklrwcgkg4@sumost.ca> Quoting Steve Robbins : > Hello MINC developers, > > The provided patch (for MINC 1) replaces use of "Status" by > "VIO_Status" to avoid a compiler error building freesurfer. On second thought, I suspect the problem can be fixed by defining VIO_PREFIX_NAMES. I'll suggest that to the bug reporter and see what results. -Steve From a.janke at gmail.com Thu Oct 19 10:24:27 2006 From: a.janke at gmail.com (Andrew Janke) Date: Thu, 19 Oct 2006 10:24:27 -0400 Subject: [MINC-development] Fwd: Bug#394071: Trouble using minc headers with gcc >= 4.0 In-Reply-To: <20061019091731.tcj6krmklrwcgkg4@sumost.ca> References: <20061019085344.vy7mlew4uggsooos@sumost.ca> <20061019091731.tcj6krmklrwcgkg4@sumost.ca> Message-ID: > > The provided patch (for MINC 1) replaces use of "Status" by > > "VIO_Status" to avoid a compiler error building freesurfer. > > On second thought, I suspect the problem can be fixed by defining > VIO_PREFIX_NAMES. I'll suggest that to the bug reporter and see what > results. That would seem to be the easier fix. -- Andrew Janke (a.janke at gmail.com || http://a.janke.googlepages.com/) Canada->Montreal Cell: +1 (514) 924 2012