|

»

»

mfiles installed with pkg -auto install are not found

View: New views

13 Messages — Rating Filter: Alert me

	mfiles installed with pkg -auto install are not found by Eric Chassande-Mottin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Bug report for Octave 3.0.0 configured for i486-pc-linux-gnu Description: ----------- mfiles installed with pkg -auto install are not found Repeat-By: --------- ~$ rm .octave_packages ~$ rm -rf octave/signal-1.0.5 ~$ octave -q octave:1> pkg -auto install octave/signal-1.0.5.tar.gz octave:2> hilbert usage: h = hilbert(f,N,dim); error: evaluating if command near line 45, column 3 error: called from `hilbert' in file `octave/signal-1.0.5/hilbert.m' octave:2> which hilbert hilbert is the user-defined function from the file octave/signal-1.0.5/hilbert.m octave:3> quit ~$ octave -q octave:1> hilbert error: `hilbert' undefined near line 1 column 1 octave:2> pkg list Package Name \| Version \| Installation directory --------------+---------+----------------------- signal \| 1.0.5 \| octave/signal-1.0.5 this is with Debian Lenny Fix: --- -- Configuration (please do not edit this section): ----------------------------------------------- uname output: Linux apcpc111 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 GNU/Linux configure opts: '--prefix=/usr' '--datadir=/usr/share' '--libdir=/usr/lib' '--libexecdir=/usr/lib' '--infodir=/usr/share/in$ Fortran compiler: /usr/bin/g77 FFLAGS: -O2 F2C: @F2C@ F2CFLAGS: @F2CFLAGS@ FLIBS: -L/usr/lib/gcc/i486-linux-gnu/3.4.6 -L/usr/lib/gcc/i486-linux-gnu/3.4.6/../../../../lib -L/usr/lib/gcc/i486$ CPPFLAGS: INCFLAGS: -I. -I. -I./liboctave -I./src -I./libcruft/misc C compiler: /usr/bin/gcc, version 4.2.3 20071123 (prerelease) (Debian 4.2.2-4) CFLAGS: -O2 CPICFLAG: -fPIC C++ compiler: /usr/bin/g++, version 4.2.3 CXXFLAGS: -O2 CXXPICFLAG: -fPIC LD_CXX: /usr/bin/g++ LDFLAGS: LIBFLAGS: -L. RLD_FLAG: -Wl,-rpath -Wl,/usr/lib/octave-3.0.0 BLAS_LIBS: -llapack-3 -lblas-3 FFTW_LIBS: -lfftw3 LIBS: -lreadline -lncurses -ldl -lhdf5 -lz -lm LEXLIB: LIBGLOB: SED: /bin/sed DEFS: -DPACKAGE_NAME="" -DPACKAGE_TARNAME="" -DPACKAGE_VERSION="" -DPACKAGE_STRING="" -DPACKAGE_BUGREPORT="" -DOCTAVE_SOURCE=1 -D_GNU_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSEPCHAR=':' -DSEPCHAR_STR=":" -D__NO_MATH_INLINES=1 -DCXX_NEW_FRIEND_TEMPLATE_DECL=1 -DCXX_ISO_COMPLIANT_LIBRARY=1 -DCXX_ABI=gnu_v3 -DHAVE_LIBM=1 -DHAVE_QHULL=1 -DHAVE_PCRE=1 -DHAVE_REGEXEC=1 -DHAVE_REGEX=1 -DHAVE_ZLIB_H=1 -DHAVE_ZLIB=1 -DHAVE_HDF5_H=1 -DHAVE_HDF5=1 -DHAVE_H5GGET_NUM_OBJS=1 -DHAVE_FFTW3=1 -DHAVE_GLPK_H=1 -DHAVE_GLPK=1 -DHAVE_CURL_CURL_H=1 -DHAVE_CURL=1 -DHAVE_IEEE754_DATA_FORMAT=1 -DF77_FUNC(name,NAME)=name ## _ -DF77_FUNC_(name,NAME)=name ## __ -DHAVE_BLAS=1 -DHAVE_SUITESPARSE_UMFPACK_H=1 -DHAVE_UMFPACK=1 -DUMFPACK_SEPARATE_SPLIT=1 -DHAVE_SUITESPARSE_COLAMD_H=1 -DHAVE_COLAMD=1 -DHAVE_SUITESPARSE_CCOLAMD_H=1 -DHAVE_CCOLAMD=1 -DHAVE_SUITESPARSE_CHOLMOD_H=1 -DHAVE_CHOLMOD=1 -DHAVE_SUITESPARSE_CS_H=1 -DHAVE_CXSPARSE=1 -DHAVE_GETHOSTNAME=1 -DHAVE_GETPWNAM=1 -DHAVE_DEV_T=1 -DHAVE_INO_T=1 -DHAVE_NLINK_T=1 -DHAVE_NLINK_T=1 -DHAVE_LONG_LONG_INT=1 -DHAVE_UNSIGNED_LONG_LONG_INT=1 -DHAVE_SIGSET_T=1 -DHAVE_SIG_ATOMIC_T=1 -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8 -DHAVE_ALLOCA_H=1 -DHAVE_ALLOCA=1 -DNPOS=std::string::npos -DHAVE_PLACEMENT_DELETE=1 -DHAVE_DYNAMIC_AUTO_ARRAYS=1 -DSTDC_HEADERS=1 -DHAVE_DIRENT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_ASSERT_H=1 -DHAVE_CURSES_H=1 -DHAVE_DLFCN_H=1 -DHAVE_FCNTL_H=1 -DHAVE_FLOAT_H=1 -DHAVE_GRP_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_LOCALE_H=1 -DHAVE_MEMORY_H=1 -DHAVE_NCURSES_H=1 -DHAVE_POLL_H=1 -DHAVE_PWD_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_POLL_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_UTSNAME_H=1 -DHAVE_TERMCAP_H=1 -DHAVE_UNISTD_H=1 -DHAVE_UTIME_H=1 -DHAVE_SSTREAM=1 -DHAVE_TERMIO_H=1 -DHAVE_SGTTY_H=1 -DHAVE_GLOB_H=1 -DHAVE_FNMATCH_H=1 -DHAVE_FNMATCH=1 -DHAVE_GLOB=1 -DHAVE_ATEXIT=1 -DHAVE_BASENAME=1 -DHAVE_BCOPY=1 -DHAVE_BZERO=1 -DHAVE_CANONICALIZE_FILE_NAME=1 -DHAVE_CHMOD=1 -DHAVE_DUP2=1 -DHAVE_ENDGRENT=1 -DHAVE_ENDPWENT=1 -DHAVE_EXECVP=1 -DHAVE_FCNTL=1 -DHAVE_FORK=1 -DHAVE_GETCWD=1 -DHAVE_GETEGID=1 -DHAVE_GETEUID=1 -DHAVE_GETGID=1 -DHAVE_GETGRENT=1 -DHAVE_GETGRGID=1 -DHAVE_GETGRNAM=1 -DHAVE_GETPGRP=1 -DHAVE_GETPID=1 -DHAVE_GETPPID=1 -DHAVE_GETPWENT=1 -DHAVE_GETPWUID=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_GETUID=1 -DHAVE_GETWD=1 -DHAVE_KILL=1 -DHAVE_LGAMMA=1 -DHAVE_LINK=1 -DHAVE_LOCALTIME_R=1 -DHAVE_LSTAT=1 -DHAVE_MEMMOVE=1 -DHAVE_MKDIR=1 -DHAVE_MKFIFO=1 -DHAVE_MKSTEMP=1 -DHAVE_ON_EXIT=1 -DHAVE_PIPE=1 -DHAVE_POLL=1 -DHAVE_PUTENV=1 -DHAVE_RAISE=1 -DHAVE_READLINK=1 -DHAVE_REALPATH=1 -DHAVE_RENAME=1 -DHAVE_RINDEX=1 -DHAVE_RMDIR=1 -DHAVE_ROUND=1 -DHAVE_SELECT=1 -DHAVE_SETGRENT=1 -DHAVE_SETLOCALE=1 -DHAVE_SETPWENT=1 -DHAVE_SETVBUF=1 -DHAVE_SIGACTION=1 -DHAVE_SIGLONGJMP=1 -DHAVE_SIGPENDING=1 -DHAVE_SIGPROCMASK=1 -DHAVE_SIGSUSPEND=1 -DHAVE_SNPRINTF=1 -DHAVE_STAT=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRPTIME=1 -DHAVE_STRSIGNAL=1 -DHAVE_SYMLINK=1 -DHAVE_TEMPNAM=1 -DHAVE_TGAMMA=1 -DHAVE_UMASK=1 -DHAVE_UNAME=1 -DHAVE_UNLINK=1 -DHAVE_USLEEP=1 -DHAVE_UTIME=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1 -DHAVE_WAITPID=1 -DHAVE_STRFTIME=1 -DHAVE_LIBDL=1 -DHAVE_DLOPEN=1 -DHAVE_DLSYM=1 -DHAVE_DLERROR=1 -DHAVE_DLCLOSE=1 -DHAVE_DLOPEN_API=1 -DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1 -DHAVE_FINITE=1 -DHAVE_ISNAN=1 -DHAVE_ISINF=1 -DHAVE_COPYSIGN=1 -DHAVE_DECL_SIGNBIT=1 -DHAVE_ACOSH=1 -DHAVE_ASINH=1 -DHAVE_ATANH=1 -DHAVE_ERF=1 -DHAVE_ERFC=1 -DHAVE_EXP2=1 -DHAVE_LOG2=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1 -DHAVE_STRUCT_STAT_ST_BLOCKS=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1 -DUSE_READLINE=1 -DEXCEPTION_IN_MATH=1 -DRETSIGTYPE=void -DHAVE_DECL_SYS_SIGLIST=1 -DHAVE_LSTAT=1 -DHAVE_MEMMOVE=1 -DHAVE_MKDIR=1 -DHAVE_MKFIFO=1 -DHAVE_MKSTEMP=1 -DHAVE_ON_EXIT=1 -DHAVE_PIPE=1 -DHAVE_POLL=1 -DHAVE_PUTENV=1 -DHAVE_RAISE=1 -DHAVE_READLINK=1 -DHAVE_REALPATH=1 -DHAVE_RENAME=1 -DHAVE_RINDEX=1 -DHAVE_RMDIR=1 -DHAVE_ROUND=1 -DHAVE_SELECT=1 -DHAVE_SETGRENT=1 -DHAVE_SETLOCALE=1 -DHAVE_SETPWENT=1 -DHAVE_SETVBUF=1 -DHAVE_SIGACTION=1 -DHAVE_SIGLONGJMP=1 -DHAVE_SIGPENDING=1 -DHAVE_SIGPROCMASK=1 -DHAVE_SIGSUSPEND=1 -DHAVE_SNPRINTF=1 -DHAVE_STAT=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRPTIME=1 -DHAVE_STRSIGNAL=1 -DHAVE_SYMLINK=1 -DHAVE_TEMPNAM=1 -DHAVE_TGAMMA=1 -DHAVE_UMASK=1 -DHAVE_UNAME=1 -DHAVE_UNLINK=1 -DHAVE_USLEEP=1 -DHAVE_UTIME=1 -DHAVE_VFPRINTF=1 -DHAVE_VSPRINTF=1 -DHAVE_VSNPRINTF=1 -DHAVE_WAITPID=1 -DHAVE_STRFTIME=1 -DHAVE_LIBDL=1 -DHAVE_DLOPEN=1 -DHAVE_DLSYM=1 -DHAVE_DLERROR=1 -DHAVE_DLCLOSE=1 -DHAVE_DLOPEN_API=1 -DENABLE_DYNAMIC_LINKING=1 -DHAVE_TIMEVAL=1 -DHAVE_FINITE=1 -DHAVE_ISNAN=1 -DHAVE_ISINF=1 -DHAVE_COPYSIGN=1 -DHAVE_DECL_SIGNBIT=1 -DHAVE_ACOSH=1 -DHAVE_ASINH=1 -DHAVE_ATANH=1 -DHAVE_ERF=1 -DHAVE_ERFC=1 -DHAVE_EXP2=1 -DHAVE_LOG2=1 -DHAVE_STRUCT_STAT_ST_BLKSIZE=1 -DHAVE_STRUCT_STAT_ST_BLOCKS=1 -DHAVE_STRUCT_STAT_ST_RDEV=1 -DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1 -DUSE_READLINE=1 -DEXCEPTION_IN_MATH=1 -DRETSIGTYPE=void -DHAVE_DECL_SYS_SIGLIST=1 -DHAVE_POSIX_SIGNALS=1 -DRETSIGTYPE_IS_VOID=1 -DHAVE_GETRUSAGE=1 -DHAVE_TIMES=1 -DYYTEXT_POINTER=1 -DGNUPLOT_BINARY="gnuplot" User-preferences (please do not edit this section): -------------------------------------------------- EDITOR = emacs EXEC_PATH = /usr/lib/octave/3.0.0/site/exec/i486-pc-linux-gnu:/usr/lib/octave/api-v32/site/exec/i486-pc-linux-gnu:/usr/lib/$ IMAGE_PATH = .:/usr/share/octave/3.0.0/imagelib PAGER = pager PS1 = \s:\#> PS2 = > PS4 = + beep_on_error = 0 completion_append_char = crash_dumps_octave_core = 1 echo_executing_commands = 0 fixed_point_format = 0 gnuplot_binary = gnuplot gnuplot_command_end = gnuplot_command_plot = pl gnuplot_command_replot = rep gnuplot_command_splot = sp gnuplot_command_title = t gnuplot_command_using = u gnuplot_command_with = w history_file = /home/ecm/.octave_hist history_size = 1024 ignore_function_time_stamp = system info_file = /usr/share/info/octave3.0.info info_program = info makeinfo_program = makeinfo max_recursion_depth = 256 output_max_field_width = 5 output_precision = 5 page_output_immediately = 0 page_screen_output = 1 print_answer_id_name = 1 print_empty_dimensions = 1 save_precision = 16 saving_history = 1 sighup_dumps_octave_core = 1 sigterm_dumps_octave_core = 1 silent_functions = 0 split_long_rows = 1 string_fill_char = struct_levels_to_print = 2 suppress_verbose_help_message = 0 _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by David Bateman :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Eric Chassande-Mottin wrote: > Bug report for Octave 3.0.0 configured for i486-pc-linux-gnu > > Description: > ----------- > > mfiles installed with pkg -auto install are not found > > Repeat-By: > --------- > > ~$ rm .octave_packages > ~$ rm -rf octave/signal-1.0.5 > ~$ octave -q > octave:1> pkg -auto install octave/signal-1.0.5.tar.gz > octave:2> hilbert > usage: h = hilbert(f,N,dim); > error: evaluating if command near line 45, column 3 > error: called from `hilbert' in file `octave/signal-1.0.5/hilbert.m' > octave:2> which hilbert > hilbert is the user-defined function from the file > octave/signal-1.0.5/hilbert.m > octave:3> quit > ~$ octave -q > octave:1> hilbert > error: `hilbert' undefined near line 1 column 1 > octave:2> pkg list > Package Name \| Version \| Installation directory > --------------+---------+----------------------- > signal \| 1.0.5 \| octave/signal-1.0.5 > Ok, the package is install, just not loaded.. What happens when you quit and restart Octave? Is the package available? Are you running as a user or as root? In any case I can't duplicate this under 3.0.0 on my machine.. Regards David -- David Bateman David.Bateman@... Motorola Labs - Paris +33 1 69 35 48 04 (Ph) Parc Les Algorithmes, Commune de St Aubin +33 6 72 01 06 33 (Mob) 91193 Gif-Sur-Yvette FRANCE +33 1 69 35 77 01 (Fax) The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by Eric Chassande-Mottin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message > > ~$ rm .octave_packages > > ~$ rm -rf octave/signal-1.0.5 > > ~$ octave -q > > octave:1> pkg -auto install octave/signal-1.0.5.tar.gz > > octave:2> hilbert > > usage: h = hilbert(f,N,dim); > > error: evaluating if command near line 45, column 3 > > error: called from `hilbert' in file `octave/signal-1.0.5/hilbert.m' > > octave:2> which hilbert > > hilbert is the user-defined function from the file > > octave/signal-1.0.5/hilbert.m > > octave:3> quit > > ~$ octave -q > > octave:1> hilbert > > error: `hilbert' undefined near line 1 column 1 > > octave:2> pkg list > > Package Name \| Version \| Installation directory > > --------------+---------+----------------------- > > signal \| 1.0.5 \| octave/signal-1.0.5 > > > Ok, the package is install, just not loaded.. > What happens when you quit > and restart Octave? Is the package available? this is what I do in the above test. hilbert.m is not loaded after a quit/restart of Octave. > Are you running as a user > or as root? In any case I can't duplicate this under 3.0.0 on my machine.. as a simple user. is there anything I can do to understand what happens ? eric. _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by David Bateman :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Eric Chassande-Mottin wrote: >> What happens when you quit >> and restart Octave? Is the package available? >> > > this is what I do in the above test. hilbert.m is > not loaded after a quit/restart of Octave. > Ok, missed that.. Then it is clear that the package has not been flagged as autoloaded at all. The signal package is autoloaded by default and so not using the "-auto" flag should work for what you want. >> Are you running as a user >> or as root? In any case I can't duplicate this under 3.0.0 on my machine.. >> > > as a simple user. > is there anything I can do to understand what happens ? > Look in ~/octave/signal-1.0.5 for a file .autoload that should be created by the install process. I can duplicate this issue and so can't really suggest a solution. As a temporary fix touch ~/octave/signal-1.0.5/.autoload should get the issue fixed at least for this package.. If you really want to try and debug this issue at about line 720 in Octave 3.0.0's version of pkg.m you'll find the code for i = length (descriptions):-1:1 if (autoload > 0 \|\| (autoload == 0 && isautoload (descriptions(i)))) fclose (fopen (fullfile (descriptions{i}.dir, "packinfo", ".autoload"), "wt")); descriptions{i}.autoload = 1; endif endfor insert a keyboard statement just inside the for-loop and see what the values of autoload, descriptions(i), isautoload (descriptions(i)) and descriptions{i}.autoload are.. Regards David > eric. > > -- David Bateman David.Bateman@... Motorola Labs - Paris +33 1 69 35 48 04 (Ph) Parc Les Algorithmes, Commune de St Aubin +33 6 72 01 06 33 (Mob) 91193 Gif-Sur-Yvette FRANCE +33 1 69 35 77 01 (Fax) The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by Eric Chassande-Mottin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message > Yes, probably in the function load_packages_and_dependencies this function doesn't appear to be executed at octave's startup. e _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by Eric Chassande-Mottin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message > > Yes, probably in the function load_packages_and_dependencies > > this function doesn't appear to be executed at octave's startup. which function does the pkg manager call at start up? thanks, eric. _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by David Bateman :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Eric Chassande-Mottin wrote: >>> Yes, probably in the function load_packages_and_dependencies >>> >> this function doesn't appear to be executed at octave's startup. >> > > which function does the pkg manager call at start up? > > thanks, > eric. > > Octave calls "pkg load auto" on start up.. D. -- David Bateman David.Bateman@... Motorola Labs - Paris +33 1 69 35 48 04 (Ph) Parc Les Algorithmes, Commune de St Aubin +33 6 72 01 06 33 (Mob) 91193 Gif-Sur-Yvette FRANCE +33 1 69 35 77 01 (Fax) The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by Ben Abbott :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Feb 15, 2008, at 11:18 AM, Eric Chassande-Mottin wrote: >>> Yes, probably in the function load_packages_and_dependencies >> >> this function doesn't appear to be executed at octave's startup. > > which function does the pkg manager call at start up? > > thanks, > eric. Take a look at ~/.octaverc If you have an editor setup to run edit ~/.octaverc Ben _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by Eric Chassande-Mottin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message mine doesn't. the bug is thus in the script that calls "pkg load auto". ~$ octave -q octave:1> pkg list Package Name \| Version \| Installation directory --------------+---------+----------------------- signal \| 1.0.5 \| octave/signal-1.0.5 octave:2> hilbert error: `hilbert' undefined near line 2 column 1 octave:2> pkg load auto octave:3> hilbert usage: h = hilbert(f,N,dim); error: evaluating if command near line 45, column 3 error: called from `hilbert' in file `octave/signal-1.0.5/hilbert.m' _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by David Bateman :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Eric Chassande-Mottin wrote: > mine doesn't. the bug is thus in the script that calls "pkg load auto". > > ~$ octave -q > > octave:1> pkg list > Package Name \| Version \| Installation directory > --------------+---------+----------------------- > signal \| 1.0.5 \| octave/signal-1.0.5 > octave:2> hilbert > error: `hilbert' undefined near line 2 column 1 > > octave:2> pkg load auto > > octave:3> hilbert > usage: h = hilbert(f,N,dim); > error: evaluating if command near line 45, column 3 > error: called from `hilbert' in file `octave/signal-1.0.5/hilbert.m' > > It appears that debian modifies the octaverc file. Check in <PREFIX>/share/octave/3.0.0/m/startup/octaverc mine contains... ## This appears here instead of in the pkg/PKG_ADD file so that --norc ## will also skip automatic loading of packages. pkg ("load", "auto"); D. -- David Bateman David.Bateman@... Motorola Labs - Paris +33 1 69 35 48 04 (Ph) Parc Les Algorithmes, Commune de St Aubin +33 6 72 01 06 33 (Mob) 91193 Gif-Sur-Yvette FRANCE +33 1 69 35 77 01 (Fax) The information contained in this communication has been classified as: [x] General Business Information [ ] Motorola Internal Use Only [ ] Motorola Confidential Proprietary _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by Eric Chassande-Mottin :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message > Take a look at ~/.octaverc > > If you have an editor setup to run > > edit ~/.octaverc > right or we can say that there is a missing "pkg load auto" in /usr/share/octave/3.0.0/m/startup/octaverc in Debian distribution. eric. _______________________________________________ Bug-octave mailing list Bug-octave@... https://www.cae.wisc.edu/mailman/listinfo/bug-octave
	Re: mfiles installed with pkg -auto install are not found by G.. :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message David Bateman wrote: Octave calls "pkg load auto" on start up.. but that means that all packages are auto-loaded, even those that do not have the auto-flag. G.
	Re: mfiles installed with pkg -auto install are not found by G.. :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message G.. wrote: David Bateman wrote: Octave calls "pkg load auto" on start up.. but that means that all packages are auto-loaded, even those that do not have the auto-flag. G. Works now with all packages updated and reinstalled. G.