[Insight-developers] Re: ITK/VNL Build Issues on Cygwin/gcc 3.2

[kent williams]

According to the changelog for vxl, all that really needs to happen is for
'#pragma interface' to be removed from the configure.in script where it's
generating
the conftest.C file to check for the need of inline instantiation.
Apparently on
Cygwin this ends up suppressing the main function, which is why the link
fails.

I've tested this by changing Insight/Code/Numerics/vxl/vcl/configure and it
works.
Ultimately the configure.in file needs correcting -- as it apparently is in
the VXL
cvs tree, but not the current VXL release -- but since few ITK developers
are
running autoconf down in the vcl directory, it should be changed in the
configure
script as well.

----- Original Message -----
From: "Lorensen, William E (Research)" <lorensen@crd.ge.com>
To: "'Bill Hoffman'" <bill.hoffman@kitware.com>; "Lydia Ng"
<lng@insightful.com>
Cc: "Kent Williams" <kent@mail.psychiatry.uiowa.edu>;
<insight-developers@public.kitware.com>
Sent: Friday, February 14, 2003 3:48 PM
Subject: RE: [Insight-developers] Re: ITK/VNL Build Issues on Cygwin/gcc 3.2


> I just tried the change on my cygwin build and all of vnl built fine. But,
I do not have an
> update-to-date autoconf.
>
> Bill, could you make the change. I realize that you are upgrading vnl, but
this will help us set a
> baseline for the upgrade.
>
> You'll need to change
> Insight/Code/Numerics/vxl/vcl/aclocal.m4
> remove the GNUC ifdef
> rerun autoconf
> check in configure and aclocal.m4
>
> Thanks,
>
> Bill
>
> -----Original Message-----
> From: Bill Hoffman [mailto:bill.hoffman@kitware.com]
> Sent: Friday, February 14, 2003 4:31 PM
> To: Lydia Ng
> Cc: Kent Williams; insight-developers@public.kitware.com
> Subject: [Insight-developers] Re: ITK/VNL Build Issues on Cygwin/gcc 3.2
>
>
> If it is fixed in vxl, then that is good news.
> When I get done upgrading our vnl to the a more recent
> vxl, then it should just work, and nothing will need
> to be ported.
>
> -Bill
>
>
>
> >Looking at the VXL dashboard and cvs looks like they have fixed this
> >problem. See
> >http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vxl/vxl/configure
> >Revision 1.11
> >
> >I am not too familiar with how "configure" works. Would you be able to
> >help port the require changes into ITK?
> >
> >Attached is the configure.log file showing the link error.
> >
> >Thanks,
> >Lydia
> >
> >
> > <<config.log>>
>
>
>
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers
>