help-octave
[Top][All Lists]
Advanced

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

Wrong copy of MINGW called in PKG UPDATE?


From: Michael L. Metts
Subject: Wrong copy of MINGW called in PKG UPDATE?
Date: Tue, 3 Dec 2013 15:58:19 -0800

Hi.  I am using Octave 3.6.4 (Mingw) on Windows 7 and I recently attempted to let Octave run an update of the installed packages.  I ran this:

PKG UPDATE

After awhile the command failed and the error messages that were generated lead me to believe that Octave was trying to run LD.EXE out of my copy of Strawberry Perl rather than the LD.EXE that’s with the copy of MINGW installed with Octave.  I’ve tried to figure out how this is happening since “c:\strawberry” is not in Octave’s EXEC_PATH but it IS in the Windows path environment variable.  I don’t see a way to break this inheritance of path variables so far. 

Anyway, I’ve been hoping to get my copy of Octave to behave itself and compile/update things properly but I’m unable to figure out how to make is use all its own resources.

Is there something I’m missing here?  If it’s not reasonable to expect my copy of Octave to run updates that lead to (need) compilation on Windows, I’m okay with that I suppose.  But, if there’s a way to fix this I’d appreciate any pointers.

Below is the output of my dump_prefs().  I don’t unfortunately have the errors it threw when I did a PKG UPDATE and I’m afraid to try it again until I have some guidance since I’m taking a class right now that uses Octave and I’d like to avoid excessive risk that I’ll hose it up to the point that it’s unusable.

Please advise.

Thanks,

Mike

octave:1> dump_prefs()

  EDITOR = C:\\Program Files (x86)\\IDM Computer Solutions\\UltraEdit\Uedit32.exe

  EXEC_PATH = C:\Octave\Octave3.6.4_gcc4.6.2\libexec\octave\3.6.4\site\exec\i686-pc-mingw32;C:\Octave\Octave3.6.4_gcc4.6

.2\libexec\octave\api-v48+\site\exec\i686-pc-mingw32;C:\Octave\Octave3.6.4_gcc4.6.2\libexec\octave\site\exec\i686-pc-min

gw32;C:\Octave\Octave3.6.4_gcc4.6.2\libexec\octave\3.6.4\exec\i686-pc-mingw32;C:\Octave\Octave3.6.4_gcc4.6.2\bin;C:\Octa

ve\Octave3.6.4_gcc4.6.2\gnuplot\bin;C:\Octave\Octave3.6.4_gcc4.6.2\mingw\bin;C:\Octave\Octave3.6.4_gcc4.6.2\mingw\msys\1

.0\bin;C:\Octave\Octave3.6.4_gcc4.6.2\gs\bin;C:\Octave\Octave3.6.4_gcc4.6.2\pstoedit;C:\Octave\Octave3.6.4_gcc4.6.2\fig2

dev

  IMAGE_PATH = .;C:\Octave\Octave3.6.4_gcc4.6.2\share\octave\3.6.4\imagelib

  PAGER = less

  PS1 = octave:\#>

  PS2 = >

  PS4 = +

  beep_on_error =

  completion_append_char =

  crash_dumps_octave_core =

  echo_executing_commands = 0

  fixed_point_format =

  gnuplot_binary = gnuplot

# gnuplot_command_end = <no value or error in displaying it>

# gnuplot_command_plot = <no value or error in displaying it>

# gnuplot_command_replot = <no value or error in displaying it>

# gnuplot_command_splot = <no value or error in displaying it>

# gnuplot_command_title = <no value or error in displaying it>

# gnuplot_command_using = <no value or error in displaying it>

# gnuplot_command_with = <no value or error in displaying it>

  history_file = C:\Users\mmetts\.octave_hist

  history_size = 1024

  ignore_function_time_stamp = system

  info_file = C:\Octave\Octave3.6.4_gcc4.6.2\share\info\octave.info

  info_program = info

  makeinfo_program = makeinfo

  max_recursion_depth = 256

  output_max_field_width = 10

  output_precision = 5

  page_output_immediately =

  page_screen_output =

# print_answer_id_name = <no value or error in displaying it>

  print_empty_dimensions =

  save_precision = 16

  saving_history =

  sighup_dumps_octave_core =

  sigterm_dumps_octave_core =

  silent_functions =

  split_long_rows =

  string_fill_char =

  struct_levels_to_print = 2

  suppress_verbose_help_message =

octave:2>


reply via email to

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