Unfortunately seems that the gccxml changes are almost 0 (I got confused by the
commits exactly one month ago).
However the builds in my pbuilder chroot went successfully, I did a cmake ..
with the parameters in rules file, and the make was successful. (did not run
dpkg or fakeroot, since the b
On Tue, 2014-07-15 at 23:14 +0200, Andreas Tille wrote:
[...]
> I could do the sponsering if needed. Please confirm that
> debian/makeSource.sh really fetches the source you are working on.
> I also think *if* I would do the upload and nobody would beat me
> I would switch to xz compression for th
Hi,
On Tue, Jul 15, 2014 at 12:24:26PM -0400, Matt McCormick wrote:
> > The build of the new gccxml was successful (one patch dropped, merged
> > upstream and nothing more to say).
> > And the rebuild of insighttoolkit4 with the new gccxml too (only tested
> > i386).
> >
> > So for this package
>>
>> so I'm packaging the new gccxml locally and rebuilding insighttoolkit4 right
>> now,
>>
>> thanks for helping with this!
>>
>> I'll report as soon as the build finishes
>
> The build of the new gccxml was successful (one patch dropped, merged
> upstream and nothing more to say).
> And the re
Hi again to all,
> Il Martedì 15 Luglio 2014 13:03, Gianfranco Costamagna
> ha scritto:
> > Hi Matt and all!
>
>
>
>> Il Lunedì 14 Luglio 2014 22:09, Matt McCormick
> ha scritto:
>> > Hi,
>>
>> First, please note I made an error regarding the GCCXML bug tracker --
>> it is still
Hi Matt and all!
> Il Lunedì 14 Luglio 2014 22:09, Matt McCormick
> ha scritto:
> > Hi,
>
> First, please note I made an error regarding the GCCXML bug tracker --
> it is still in the old location. However, Steve's patch has now been
> merged upstream.
>
> I was able to reproduce the build e
Hi,
First, please note I made an error regarding the GCCXML bug tracker --
it is still in the old location. However, Steve's patch has now been
merged upstream.
I was able to reproduce the build error, but it only occurs when using
the gccxml package. The build completes fine with a local build
I will see if I can reproduce the build error.
As a side note, the GCCXML bug tracker has moved (now at the
gccxml/gccxml project on GitHub). I've created a pull request for
Steve's stl algo patch here:
https://github.com/gccxml/gccxml/pull/8
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ.
> Il Mercoledì 2 Luglio 2014 13:15, Gert Wollny
> The failing command seems to be
>
> /usr/bin/gccxml -fxml-start=_cable_
> -fxml=/«PKGBUILDDIR»/BUILD/Wrapping/Modules/ITKCommon/vcl_complex.xml
>
--gccxml-gcc-options
/«PKGBUILDDIR»/BUILD/Wrapping/Modules/ITKCommon/gcc_xml.inc
> -DCSWIG -DCABL
Hi,
> Il Mercoledì 2 Luglio 2014 13:15, Gert Wollny ha
> scritto:
> > My bad, I got irritated by the parallel build. The failing command seems
> to be
>
> /usr/bin/gccxml -fxml-start=_cable_
> -fxml=/«PKGBUILDDIR»/BUILD/Wrapping/Modules/ITKCommon/vcl_complex.xml
> --gccxml-gcc-options
> /
My bad, I got irritated by the parallel build. The failing command seems
to be
/usr/bin/gccxml -fxml-start=_cable_
-fxml=/«PKGBUILDDIR»/BUILD/Wrapping/Modules/ITKCommon/vcl_complex.xml
--gccxml-gcc-options
/«PKGBUILDDIR»/BUILD/Wrapping/Modules/ITKCommon/gcc_xml.inc -DCSWIG
-DCABLE_CONFIGURATION
> Il Mercoledì 2 Luglio 2014 12:50, Gert Wollny ha
> scritto:
> >T here must be something wrong with your setup because what is failing is
> a plain CC compile command
>
> /usr/bin/cc
>
> that should never include the files from
>
> /usr/share/gccxml-0.9/GCC/4.9/
>
> as it does in this b
There must be something wrong with your setup because what is failing is
a plain CC compile command
/usr/bin/cc
that should never include the files from
/usr/share/gccxml-0.9/GCC/4.9/
as it does in this build.
Besides, from the compiler flags SSE is not enabled, and unless g++-4.9
on i386 s
13 matches
Mail list logo
