Message-Id: <199903120526.FAA26074@out5.ibm.net>
From: "Mark E." <snowball3 AT usa DOT net>
To: djgpp-workers AT delorie DOT com
Date: Fri, 12 Mar 1999 00:26:20 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: DJGPP preprocessor and link command specs
In-reply-to: <4B9162DF.19990311214213.FOO-3CFC.frank@goedel.fjf.gnu.de>
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> That's why I think that the DJGPP compiler should dump the
> LINK_COMMAND_SPECS (otherwise, e.g., a Linux gpc when called with
> `-b i386-pc-go32' will not know about the link command specs and
> will not be able to link correctly for DJGPP). If there is any
> problem with dumping the LINK_COMMAND_SPECS, please tell me what it
> is -- up to know, I don't know of any problem.
> 

The problem seems to be be that 'gcc -dumpspecs' does not dump 
*link_command since it is treated specially. So it is a gcc/egcs issue, 
not a DJGPP issue (sort of). Not many ports use *link_command, so I 
doubt the issue has come up much if at all with the compiler 
developers.

The fix appears to be easy. Andris, below is an untested patch for the 
CVS version of gcc/gcc.c that dumps *link_command after the other 
specs. I'll send this patch on to the egcs compiler people also.

*** gcc/gcc.c.orig	Tue Mar  2 09:46:56 1999
--- gcc/gcc.c	Fri Mar 12 00:09:48 1999
***************
*** 2721,2730 ****
--- 2721,2732 ----
  	{
  	  struct spec_list *sl;
  	  init_spec ();
  	  for (sl = specs; sl; sl = sl->next)
  	    printf ("*%s:\n%s\n\n", sl->name, *(sl->ptr_spec));
+           if (link_command_spec)
+             printf ("*link_command:\n%s\n\n", link_command_spec);
  	  exit (0);
  	}
        else if (! strcmp (argv[i], "-dumpversion"))
  	{
  	  printf ("%s\n", spec_version);

--- 
Mark Elbrecht
snowball3 AT usa DOT net http://members.xoom.com/snowball3/