This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>
> Don Bowman <don@pixsci.com> writes:
> > When building the CVS image of today (march 24), I find
> > that cccp.exe cannot be built on a winnt system. It is
> > missing -ladvapi32 on the end of the link line.
>
> Don,
>
> This is only needed for stage1 compiler build, so just add:
>
> CLIB = -ladvapi32
>
> to gcc/Makefile and go on from there. The subsequent stages will
> automatically add this (cf: gcc/config/i386/cygwin32.h).
>
> I usually recommend that people pick up pre-build binaries
> from my site
> which already these changes and quite a few more, and then use that to
> bootstrap newer versions instead of using the development tools
> supplied with Cygwin32 b19. See my Gnu-Win32 project page:
>
Thanks for the advice. However, since I am building a cross-compiler,
I'm not sure its pertinent: gcc/config/i386/cygwin32.h doesn't
get used.
My question was actually: should configure fixed to add -ladvapi32?
Or should the compiler on my system do that automatically? I think
you have answered that my compiler should do that automatically,
and that I should edit my specs file
--don
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |