java - Linux javac command erroring on wildcard in classpath -
i running windows 7 java version 1.6.0_31-b05 on pc, , computerlab's network linux (fedora, possibly version 13) running java version 1.6.0_35-b10.
i have c:\myproject
(et al) directory, src
, lib
, , bin
subdirectories.
- the
src
folder contains of source code in tree structure, corresponds java packages. - the
lib
directory contains jar files.
i have re-created tree in linux, under ../myproject
(et al).
when attempt compile in dos,
..\myproject\src
directory, command below, works fine:javac -cp ".;../bin;../lib/*" -d ../bin org/unlv/schillerlab/motif_diversity/step02/*.java
when attempt compile in linux,
../myproject/src
directory, message incorrect classpath:../lib/*
:javac -cp ".:../bin:../lib/*" -d ../bin org/unlv/schillerlab/motif_diversity/step02/*.java
the computerlab network location accessible both dos , linux. in linux, first created ../myproject/src
, ../myproject/lib
, , ../myproject/bin
directories. then, in dos, copied necessary files c
drive ../myproject/src01
, ../myproject/lib01
. then, in linux, used cp -av
command populate src
, lib
src01
, lib01
, respectively. therefore, don't think there linux permissions problem.
in linux, ../myproject/src
location, issuing ls ../lib
shows (sibling) lib
directory contain jar files. have tried linux javac
command absolute path lib
directory; no joy.
similarly, tried removing quote ("
) marks -cp
clause; no joy.
could problem running old version of fedora? if not, 1 have hypothesis problem is?
wildcard expansion may behave differently on linux on windows: in unixlike systems, shells duty perform wildcard expansion before arguments passed executable; on windows each programs own duty wildcard expansion (if @ all). in doubt replace javac
echo
see how wildcards expanded! , should rather use -sourcepath
option javac
define source location (can't tell if works, must have been 10+ years since last used that...)
Comments
Post a Comment