Re: Adding -R or -rpath options to the specs file?

[Kyle McDonald <Kyle dot McDonald at east dot sun dot com>]

Mark Martin wrote:
> 
> The relevant portion of the gcc man page is available online.  For gcc 3.0,
> see
> 
> http://gcc.gnu.org/onlinedocs/gcc-3.0/gcc_3.html#SEC18
> 
> With luck, spec files for gcc 2.8.1 will follow the same syntax.  I'm not an
> expert so I can't make a definitive statement.
> 

	Thanks for the pointer Mark.

	I read through the syntax description, but the solution
	still escapes me. I was able to just add the option to 
	the specs file, and it did show up in the command line.

	I just wasn't able to make it only show up for C++ linking.
	In 2.8.1 only libstdc++ is a shared object. libgcc.a is
	still static. I'd rather not add this for all the C only
	programs that get built - though when libgcc.a is shared
	in gcc 3.0 that may be unavoidable.

	Anyone else have any Ideas to determin wether or not
	the current objects being linked were c++ files? Also
	should I do anything to stop this option from being
	passed to the linker when we are only doing static linking?
	or does that even matter?

		-Kyle


-- 
				   _
-------------------------------ooO( )Ooo-------------------------------
Kyle J. McDonald		 (o o)	       Systems Support Engineer
Sun Microsystems Inc.		 |||||			    
High End Server Engineering			  Kyle.McDonald@Sun.COM
1 Network Drive BURL03-403	 \\\//	        voice:   (781) 442-2184
Burlington, MA 01803		 (o o)            fax:   (781) 442-1646
-------------------------------ooO(_)Ooo-------------------------------