dotgnu-pnet
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pnet-developers] [bug #5243] cscc doesn't accept full path for source f


From: nobody
Subject: [Pnet-developers] [bug #5243] cscc doesn't accept full path for source file
Date: Sat, 13 Sep 2003 01:20:16 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

=================== BUG #5243: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5243&group_id=353

Changes by: Rhys Weatherley <address@hidden>
Date: Sat 09/13/2003 at 05:20 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | Invalid                   | Fixed


------------------ Additional Follow-up Comments ----------------------------
OK, I see the problem now - fix committed to CVS.

It would probably be better to only use cscc options, however.



=================== BUG #5243: FULL BUG SNAPSHOT ===================


Submitted by: bbulten                 Project: DotGNU Portable.NET          
Submitted on: Fri 09/12/2003 at 19:17
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  None                    Status:  Closed                       

Summary:  cscc doesn't accept full path for source file

Original Submission:  When compiling a source file using the fully qualified 
path, in addition to the '-t' option, cscc reports it as an 'unrecognized 
option.'

For example:

cscc -o /home/bryan/tmp/Test.exe /home/bryan/tmp/Test.cs 

Works fine.  But:

cscc -t:winexe -o /home/bryan/tmp/Test.exe /home/bryan/tmp/Test.cs

Outputs:

cscc: unrecognized option `/home/bryan/tmp/Test.cs'
cscc: No input files

Or perhaps I'm doing something wrong.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Sat 09/13/2003 at 05:20       By: rweather
OK, I see the problem now - fix committed to CVS.

It would probably be better to only use cscc options, however.

-------------------------------------------------------
Date: Sat 09/13/2003 at 03:26       By: bbulten
Same deal.

address@hidden cscc -out:/home/bryan/tmp/Test.exe /home/bryan/tmp/Test.cs
cscc: unrecognized option `/home/bryan/tmp/Test.cs'
cscc: No input files


-------------------------------------------------------
Date: Sat 09/13/2003 at 02:41       By: rweather
You're mixing up csc-style and cscc-style options, which is
causing the confusion.  Either remove "-t:winexe", which
isn't needed anyway, or use "-out:filename" instead of
"-o filename".


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=5243&group_id=353

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]