• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bad path element warning in Java build transcript
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bad path element warning in Java build transcript


  • Subject: Re: Bad path element warning in Java build transcript
  • From: David Ewing <email@hidden>
  • Date: Wed, 10 May 2006 13:39:15 -0600

This is a known issue. You can safely ignore the issue.

The problem is that the jam-based build of Java projects always passes these extra directories in the class path to the compiler, even if they don't exist.

Dave


On May 10, 2006, at 11:19 AM, Andrea XFox Govoni wrote:

Greg Guerin ha scritto:

warning: [path] bad path element "/Users/xfox/Library/Java": no such
file or directory
warning: [path] bad path element "/Network/Library/Java": no such file
or directory
2 warnings


They appears right after the JavaCompile.default transcript block.

I was seeing them in my own recently updated project because the Java
compiler had been set to 'jikes' instead of 'javac'. When I switched to
'javac', the warnings disappeared. Switch back to 'jikes' and they
reappear.

I checked the Java compiler and it's set to javac.
I tried to switch to jikes and I saw the warnings you are referring to:
they are very similar to the warnings I reported but they are written
slightly different.
However, I think I found the cause of my warnings.
I noticed that they came up only in my Debug and Development
configurations and not in the Deployment one, so I played a bit with the
parameters and found that they appears only in the configurations with
the non-standard option -Xlint set in the "Other Java Compiler Flags" of
the "Java Compiler Settings" section of the target.
I further tracked it down to the specific -Xlint:path option.
Add it to your Java compiler flags and the warnings should show up.
To see all non-standard options: javac -X


I don't know if this is worth a bug report… is right that javac checks
for paths that by default don't exist?

--
Andrea "XFox" Govoni

AIM/iChat/ICQ: email@hidden
Yahoo! ID: xfox82
Skype Name: draykan

PGP
KeyID: 0x212E69C1
Fingerprint: FBE1 CA7D 34BE 4A53 9639  5C36 B7A0 605F 212E 69C1
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: Bad path element warning in Java build transcript (From: Greg Guerin <email@hidden>)
 >Re: Bad path element warning in Java build transcript (From: "Andrea \"XFox\" Govoni" <email@hidden>)

  • Prev by Date: Re: A problem about StripAddress
  • Next by Date: Any predefined macro for current function?
  • Previous by thread: Re: Bad path element warning in Java build transcript
  • Next by thread: Turning off 'enumeral mismatch' warnings?
  • Index(es):
    • Date
    • Thread