[Octave-bug-tracker] [bug #45509] communications-1.2.1 fails during package install in octave-4.0.0

[Mike Miller]

Update of bug #45509 (project octave):

                  Status:                    None => Need Info              
             Assigned to:                    None => mtmiller               
                 Release:                   4.0.0 => other                  

    _______________________________________________________

Follow-up Comment #1:

Thanks for your bug report. I can't reproduce this error. Are you sure your
Octave 4.0.0 installation was done completely and correctly?

Can you paste the configure part of the communications package install output,
the lines that start with "checking for" and "checking whether"? I get the
following:


checking for mkoctfile... /usr/local/bin/mkoctfile-4.0.0 --verbose
checking for octave... /usr/local/bin/octave-4.0.0
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for a sed that does not truncate output... /bin/sed
checking for Octave HDF5 preprocessor flags... 
checking for Octave HDF5 linker flags... 
checking for Octave HDF5 libraries... -lhdf5
checking for octave_hdf5_id type... yes
checking for octave_base_value::gripe_load and
octave_base_value::gripe_save... yes
checking whether octave_base_value::print is const-qualified... no


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45509>

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