This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: symbols/vms?


Cool, I can certainly wait. Tristan, can you tell me your configure line and where you are putting headers/libraries? Perhaps it is a cascade from me not having those setup well.
 
 
I'm not an admin, so I'd like everything under $HOME or SYS$LOGIN, whatever.
Though there are already "standard" headers in..can't remember where but not hard to find searching the web and the machine..
 
 
I could make copies of them in $HOME though, esp. since I made a few small edits to the headers (should be the subject of a bug about fixincludes and what it should do here..)
 
 
 WALLIS> cat 1.c
int main() { }
 WALLIS> cc1 1.c
wallis$dkb500:[jaykrell.install]cc1.exe;2: error: /gnu/local/include: file speci
fication syntax error
wallis$dkb500:[jaykrell.install]cc1.exe;2: error: /gnu/include: file specificati
on syntax error
wallis$dkb500:[jaykrell.install]cc1.exe;2: error: //gcc/alpha-dec-vms/4_5_0/incl
ude: file specification syntax error
wallis$dkb500:[jaykrell.install]cc1.exe;2: error: //gcc/alpha-dec-vms/4_5_0/incl
ude-fixed: file specification syntax error
wallis$dkb500:[jaykrell.install]cc1.exe;2: error: //alpha-dec-vms/include: file
specification syntax error
wallis$dkb500:[jaykrell.install]cc1.exe;2: out of memory allocating 3233808385 b

 
 - Jay


----------------------------------------
> Subject: Re: symbols/vms?
> From: gingold@adacore.com
> Date: Tue, 25 May 2010 14:33:44 +0200
> CC: binutils@sourceware.org
> To: jay.krell@cornell.edu
>
>
> On May 25, 2010, at 2:28 PM, Jay K wrote:
>
>>
>> It seems like -g doesn't work with Alpha/VMS. ?
>> (yeah, could be gcc, could be as, could be ld)
>
> Not yet.
> I am committing patches to do that. I hope to commit the latest patch (for that) tomorrow.
>
>> I'm using my own cross gcc/as/ld. Some small patches to get it to work.
>> Clearly it largely works, cool.
>
> Congrats!
>
>> I'd like to break on xmalloc_failed in cc1.exe.
>> Since it is being passed a large value and failing.
>
> Interesting. AFAIR, we never encountered this issue (well, unless using
> pathological tests)
>
> Tristan.
> 		 	   		  


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]