This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] PR/5944: Support windres using correct gcc for mingw64


On 3/18/08, NightStrike <nightstrike@gmail.com> wrote:
> On 3/18/08, Kai Tietz <Kai.Tietz@onevision.com> wrote:
> > Nick Clifton <nickc@redhat.com> wrote on 18.03.2008 11:56:14:
> >
> > > Hi Kai,
> > >
> > > > 2008-03-17  Kai Tietz  <Kai.Tietz@onevision.com>
> > > >
> > > >         PR/5944
> > > >         * binutils-all/windres/windres.exp: Add cross compiler support
> > > >         for mingw64.
> > >
> > > Approved, but...
> > >
> > > > +# For none winsup using targets use the target gcc compiler
> > > > +if {[istarget "x86_64-*-mingw*"] } {
> > >
> > > Can this problem also occur for the i686-*-mingw* target ?  If so,
> > > shouldn't it be included in this test ?
> > I can modify the code, that always the content of $CC is used as
> > preprocessor for windres. The problem can happen for all mingw cross
> > compilers using just the binutils snapshot for build without the winsup/
> > directory in base.
> > Additionally there is still a lack in supporting the build of cross
> > binutils itself. For this we would need the --with-sysroot path from
> > configure, which is unavailable for testsuite AFAIK. Additionally the
> > define '-D_WIN32' should be passed to the windres, if cross-compiling is
> > done.
>
> --with-sysroot path can be made available when make builds the
> site.exp file.  See bug report here:
>
> http://sourceware.org/bugzilla/show_bug.cgi?id=5944
>


Also, keep in mind that using the cross compiler as the preprocessor
requires that you do 'make all-gcc' before you can run 'make check' on
binutils.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]