Date: Sun, 20 Feb 2000 11:57:34 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Rossz Vámos-Wentworth cc: djgpp AT delorie DOT com Subject: Re: building binutils and cross-compiler In-Reply-To: <38aed9bf_2@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 EAA18861 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 Sat, 19 Feb 2000, Rossz Vámos-Wentworth wrote: > First off, I discovered I had to replace "ln -s" with "cp -f" since symbolic > links are not supported by DJGPP (no surprise). Perhaps there should be a > test in "configure" to do this automatically. The script does test this, but in a way that makes it think symlinks work. You should be able to override this by setting LN_S in the environment. The file config.site which comes iwth the latest Bash port already does that, so I'm curious how come configure wasn't picking that in your case. > The major problem I am having is getting prefixes on the built files. I've > included --"program-prefix=h8300-hms-" on the command line but that doesn't > make a difference. I examined the makefile that is created in it does > contain "transform = s,^,h8300-hms-,". when I run make, I end up with > "gas-new.exe", etc. This is expected: the prefix is only prepended when you say "make install". > Running "make install" results in a multilevel > directory structure with some files with that prefix, but not the > executable. Please see why doesn't Make prepend the prefix when it installs the executable. IIRC, it should. If you cannot figure this out, please post the relevant fragments of the Makefile(s). > I'm also experiencing problems building the cross compiler (gcc-2.95.2), but > I suspect it is related to this problem. When it attempts to build the > h8300 runtime library it chokes on assembler code, dumping out errors about > instructions not being i386 instructions. Add -v to the compiler's command line and watch the assembler it invokes. One way of forcing it to invoke the correct assembler is to set GCC_EXEC_PREFIX in the environment, see the GCC docs for the description of this feature.