Date: Tue, 22 Feb 2000 11:51:40 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Rossz Vámos-Wentworth cc: djgpp AT delorie DOT com Subject: Re: More on building a cross compiler - help needed In-Reply-To: <38b0aa3f_1@news.jps.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id EAA26976 Reply-To: djgpp AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 20 Feb 2000, Rossz Vámos-Wentworth wrote: > My main problem seems to be in building the cross libraries. Is tinfo.cc part of a library? I don't think so, it seems it's part of the C++ compiler which you do need. > I don't need > them, so how do I surpress their builds so that the "make install" ( or > "make install-gcc-cross" ? ) command will work for the executables? You could try invoking Make with the -k switch, but if that doesn't help, you will have to solve the problems somehow. > ./libgcc2.c:995: warning: right shift count >= width of type > > Is this normal? No, it means that the offending line invokes an undefined behavior. I'd suggest to solve this; post the code fragment if you cannot figure this out. > Since they are only warning errors and I don't care about > the runtime libraries, I didn't worry. How so? libgcc.a is an essential part of the compiler, you might be unable to produce executables that can be run on the target without libgcc. > In file included from ./cp/tinfo.cc:32: > include/new:28: `operator new' takes type `size_t' as first parameter [snip] > I looked inside the problem file. The first parameter IS 'size_t'. Perhaps > a redefinition earlier in the build? Add -save-temps to the compiler switches and examine the *.ii files it leaves behind. You will then see what does cc1 see on that line. > In desperation I tried to copy xgcc.exe and related executables manually, I don't think this is a good idea: you haven't produced the cross-compiler yet, so this is not going to be solved by a manual installation.