Hi, I just tried to compile the package and got this weird linker error. Any thought?

$ make MK toolbox/mex/mexa64/ CC toolbox/mex/mexa64/vl_mser.d CC toolbox/mex/mexa64/vl_erfill.d CC toolbox/mex/mexa64/vl_localmax.d CC toolbox/mex/mexa64/vl_pegasos.d CC toolbox/mex/mexa64/vl_ihashfind.d CC toolbox/mex/mexa64/vl_homkermap.d CC toolbox/mex/mexa64/vl_alldist.d CC toolbox/mex/mexa64/vl_alldist2.d CC toolbox/mex/mexa64/vl_binsearch.d CC toolbox/mex/mexa64/vl_simdctrl.d CC toolbox/mex/mexa64/vl_binsum.d CC toolbox/mex/mexa64/vl_ihashsum.d CC toolbox/mex/mexa64/vl_kdtreebuild.d CC toolbox/mex/mexa64/vl_samplinthist.d CC toolbox/mex/mexa64/vl_getpid.d CC toolbox/mex/mexa64/vl_twister.d CC toolbox/mex/mexa64/vl_kdtreequery.d CC toolbox/mex/mexa64/vl_inthist.d CC toolbox/mex/mexa64/vl_lbp.d CC toolbox/mex/mexa64/vl_version.d CC toolbox/mex/mexa64/vl_rodr.d CC toolbox/mex/mexa64/vl_irodr.d CC toolbox/mex/mexa64/vl_quickshift.d CC toolbox/mex/mexa64/vl_imwbackwardmx.d CC toolbox/mex/mexa64/vl_tpsumx.d CC toolbox/mex/mexa64/vl_imdisttf.d CC toolbox/mex/mexa64/vl_imintegral.d CC toolbox/mex/mexa64/vl_imsmooth.d CC toolbox/mex/mexa64/vl_dsift.d CC toolbox/mex/mexa64/vl_ubcmatch.d CC toolbox/mex/mexa64/vl_siftdescriptor.d CC toolbox/mex/mexa64/vl_sift.d CC toolbox/mex/mexa64/vl_aibhist.d CC toolbox/mex/mexa64/vl_aib.d CC toolbox/mex/mexa64/vl_ikmeanspush.d CC toolbox/mex/mexa64/vl_ikmeans.d CC toolbox/mex/mexa64/vl_hikmeans.d CC toolbox/mex/mexa64/vl_kmeans.d CC toolbox/mex/mexa64/vl_hikmeanspush.d MK bin/glnxa64/ MK bin/glnxa64/objs/ CC bin/glnxa64/test_vec_comp.d CC bin/glnxa64/test_threads.d CC bin/glnxa64/test_stringop.d CC bin/glnxa64/test_rand.d CC bin/glnxa64/test_qsort-def.d CC bin/glnxa64/test_nan.d CC bin/glnxa64/test_mathop.d CC bin/glnxa64/test_mathop_abs.d CC bin/glnxa64/test_imopv.d CC bin/glnxa64/test_host.d CC bin/glnxa64/test_heap-def.d CC bin/glnxa64/test_getopt_long.d CC bin/glnxa64/sift.d CC bin/glnxa64/mser.d CC bin/glnxa64/aib.d CC bin/glnxa64/objs/stringop.d CC bin/glnxa64/objs/sift.d CC bin/glnxa64/objs/rodrigues.d CC bin/glnxa64/objs/random.d CC bin/glnxa64/objs/quickshift.d CC bin/glnxa64/objs/pgm.d CC bin/glnxa64/objs/pegasos.d CC bin/glnxa64/objs/mser.d CC bin/glnxa64/objs/mathop_sse2.d CC bin/glnxa64/objs/mathop.d CC bin/glnxa64/objs/lbp.d CC bin/glnxa64/objs/kmeans.d CC bin/glnxa64/objs/kdtree.d CC bin/glnxa64/objs/imopv_sse2.d CC bin/glnxa64/objs/imopv.d CC bin/glnxa64/objs/ikmeans.d CC bin/glnxa64/objs/host.d CC bin/glnxa64/objs/homkermap.d CC bin/glnxa64/objs/hikmeans.d CC bin/glnxa64/objs/getopt_long.d CC bin/glnxa64/objs/generic.d CC bin/glnxa64/objs/dsift.d CC bin/glnxa64/objs/array.d CC bin/glnxa64/objs/aib.d CC bin/glnxa64/objs/aib.o CC bin/glnxa64/objs/array.o CC bin/glnxa64/objs/dsift.o CC bin/glnxa64/objs/generic.o CC bin/glnxa64/objs/getopt_long.o CC bin/glnxa64/objs/hikmeans.o CC bin/glnxa64/objs/homkermap.o CC bin/glnxa64/objs/host.o CC bin/glnxa64/objs/ikmeans.o CC bin/glnxa64/objs/imopv.o CC bin/glnxa64/objs/imopv_sse2.o CC bin/glnxa64/objs/kdtree.o CC bin/glnxa64/objs/kmeans.o vl/kmeans.c:546:11: warning: variable ‘allDone’ set but not used [-Wunused-but-set-variable] vl/kmeans.c:546:11: warning: variable ‘allDone’ set but not used [-Wunused-but-set-variable] CC bin/glnxa64/objs/lbp.o CC bin/glnxa64/objs/mathop.o CC bin/glnxa64/objs/mathop_sse2.o CC bin/glnxa64/objs/mser.o CC bin/glnxa64/objs/pegasos.o CC bin/glnxa64/objs/pgm.o CC bin/glnxa64/objs/quickshift.o CC bin/glnxa64/objs/random.o CC bin/glnxa64/objs/rodrigues.o CC bin/glnxa64/objs/sift.o CC bin/glnxa64/objs/stringop.o CC bin/glnxa64/libvl.so CC bin/glnxa64/aib ******* Offending Command: cc '-std=c99' '-Wall' '-Wextra' '-Wno-unused-function' '-Wno-long-long' '-Wno-variadic-macros' '-I.' '-DNDEBUG' '-O3' '-lm' '-Wl,--rpath,$ORIGIN/' '-Lbin/glnxa64' '-lvl' 'src/aib.c' '-o' 'bin/glnxa64/aib' ******* Error Code: 1 ******* Command Output: /tmp/cclyk1YX.o: In function main': aib.c:(.text.startup+0x43d): undefined reference tovl_aib_new' aib.c:(.text.startup+0x448): undefined reference to vl_aib_process' aib.c:(.text.startup+0x47d): undefined reference tovl_aib_delete' collect2: ld returned 1 exit status make: *** [bin/glnxa64/aib] Error 1

I got the error below after I upgrade Matlab from 2016b to 2017a: Invalid MEX-file

'.../MATLAB/vlfeat/vlfeat-0.9.20/toolbox/mex/mexmaci64/vl_version.mexmaci64':
Missing dependent shared libraries:
'@loader_path/libvl.dylib' required by
'.../MATLAB/vlfeat/vlfeat-0.9.20/toolbox/mex/mexmaci64/vl_version.mexmaci64'

Plus a bunch of missing symbols like:

Missing symbol '___tolower' required by
'.../MATLAB/vlfeat/vlfeat-0.9.20/toolbox/mex/mexmaci64/vl_version.mexmaci64'

I did not make any change on vlfeat folder, and 'libvl.dylib' is right under the '/toolbox/mex/mexmaci64/' folder.

Is someone able to run vlfeat with Matlab 2017a on MacOS?

Hi,

I got this error when I compute vl_phow

"Attempt to execute SCRIPT vl_imsmooth as a function"

Someone gave this solution: You are getting this error because your path ".../vlfeat-0.9.16/toolbox/imop/vl_imsmooth.m" has a higher precedence than " ...../vlfeat-0.9.16/toolbox/mex/mexa64/vl_imsmooth.mexa64" so you can simply run

pathtool

I tried it, but it doesn't work. Thanks

novi

In vlfeat-0.9.19\toolbox\fisher\vl_fisher, Line 151:

OUT(ENC) = mxCreateNumericMatrix (dimension * numClusters * 2, 1, classID, mxREAL) ;

the returned fisher code will always be one column, no matter how many columns exist in the input feature matrix!

I am using sift from command line on mac and got the following error message:

sift(490,0x7fff89999380) malloc: *** mach_vm_map(size=4342377827252789248) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
sift(490,0x7fff89999380) malloc: *** mach_vm_map(size=17369511309011156992) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
sift: err: Could not allocate enough memory. (2)

The code I am working on is (Python):

params="--edge-thresh 10 --peak-thresh 5"

if imagename[-3:] != 'pgm':
  # create a pgm file
  im = Image.open(imagename).convert('L')
  im.save('tmp.pgm')
  imagename = 'tmp.pgm'

cmmd = str("sift " + imagename + " --output=" + resultname + " " + params)
os.system(cmmd)

Image using is of size: 1280 × 1000, 333 KB.

Anyone has idea about how to solve this problem? Thanks.

Hi,

we're seeing different results / features detected in v0.9.20 depending on whether we set STD_CFLAGS to x86-64 or broadwell.

We're using covdet feature detection + sift featue descriptors.

Is it expected that the AVX and non-AVX implementations give different results?

Thanks!

The function vl_covdet_extract_laplacian_scales_for_frame() in covdet.c (around line 2043) uses VL_COVDET_DOG_DEF_PEAK_THRESHOLD as the peak threshold instead of self->peakThreshold.

OK, so I was trying to compile vlfeat on OSX 10.9.3 with XCode 5.1.1 and clang-503.0.40 for Matlab 2014a and I encountered two different errors:

1. Unable to find Matlab executable

Symptoms

Running make info yields:

** MATLAB support
MATLAB support disabled (MEX not found)
        mex_src = ./toolbox/aib/vl_aib.c ./toolbox/aib/vl_aibhist.c ...
        mex_tgt = toolbox/mex/mexmaci64/vl_aib.mexmaci64 toolbox/mex/mexmaci64/vl_aibhist.mexmaci64 ...
        mex_dep = toolbox/mex/mexmaci64/vl_aib.d toolbox/mex/mexmaci64/vl_aibhist.d ...
          m_src = ./toolbox/aib/vl_aib.m ./toolbox/aib/vl_aibcut.m ...
          m_lnk = toolbox/noprefix/aib.m toolbox/noprefix/aibcut.m ...
        mex_dll = toolbox/mex/mexmaci64/libvl.dylib
    MATLAB_PATH = 
     MATLAB_EXE = /bin/matlab
            MEX = mex
...

which obviously shows that Matlab couldn't be found.

Running mex on the command line yields:

Not enough input arguments.

So matlab is definitely on the path.

Solution

Run:

make MATLAB_PATH=/Applications/MATLAB_R2014a.app

2. Linker error (-exported_symbols_list)

Symptoms

Detected compiler: clang 50100
Clang does not support OpenMP yet, disabling.
            MEX toolbox/mex/mexmaci64/vl_aib.mexmaci64
Building with 'Xcode with Clang'.
ld: can't open -exported_symbols_list file: /Applications/MATLAB_R2014a.app/extern/lib/$Arch/$MAPFILE
clang: error: linker command failed with exit code 1 (use -v to see invocation)

make: *** [toolbox/mex/mexmaci64/vl_aib.mexmaci64] Error 255

Seems like $Arch and $MAPFILE are not properly set?

Solution

--- make/matlab.mak
+++ make/matlab.mak
@@ -122,7 +122,7 @@
 -arch x86_64 \
 -Wl,-syslibroot,$(SDKROOT) \
 -mmacosx-version-min=$(MACOSX_DEPLOYMENT_TARGET) \
--bundle -Wl,-exported_symbols_list,$(MATLAB_PATH)/extern/lib/\$$Arch/\$$MAPFILE \
+-bundle -Wl,-exported_symbols_list,$(MATLAB_PATH)/extern/lib/maci64/mexFunction.map \
 $(if $(DISABLE_OPENMP),,-L$(MATLAB_PATH)/sys/os/$(ARCH)/) \
 $(call escape,$(STD_LDFLAGS))'
 endif

This also appears on L105 for the 32-bit Mac compilation. Not sure why this isn't set? But setting it explicitly definitely seems to work.

I try to use g++ to compile the simplest "Hello World" program of vlfeat. My system is Ubuntu 12.04 LTS 64-bit.

I can compile successfully, but when I run it, it failed with message like this: "error while loading shared libraries: libvl.so: cannot open shared object file: No such file or directory"

Anyone tell me how to fix it?

I'm using vlfeat in a hadoop pipes process, thus instead of installing vlfeat shared libraries on all hadoop nodes i just create a static library of vlfeat and compile it into the rest of my code.

Maybe somebody else would like to have option for static library and not just shared library of vlfeat

The output of make command reveals that AVX gets disabled when using gcc version 8.

$ make
...
Detected compiler: gcc 8
GCC <= 4.6.0 detected, disabling AVX.
...
$ gcc --version
gcc (Debian 8.3.0-6) 8.3.0

The following line in Makefile needs an update for newer versions of gcc.

Hi there! When sifting through the documentation, I found several places where markup seams to leak through into the HTML output, for example here(Formulas in the Technical Details section) or here (throughout the text). The unhandled markup shows like this: The poses \(u,u'\) of \(R=u[R_0]\) and \(R' = u'[R_0]\) are then related ... \[ \mathrm{DoG}_{\sigma(o,s)} = I_{\sigma(o,s+1)} - I_{\sigma(o,s)} \] ... I'm using Firefox 104.0 (64-Bit) on Ubuntu 20.04, but I doubt it's a browser issue.

vlfeat is available as a port in vcpkg, a C++ library manager that simplifies installation for vlfeat and other project dependencies. Documenting the install process here will help users get started by providing a single set of commands to build vlfeat, ready to be included in their projects.

We also test whether our library ports build in various configurations (dynamic, static) on various platforms (OSX, Linux, Windows: x86, x64) to keep a wide coverage for users.

I'm a maintainer for vcpkg, and here is what the port script looks like. We try to keep the library maintained as close as possible to the original library. :)

When I wrote codes like this: [index, distance] = vl_kdtreequery(kdtree, X, Q, 'NumNeighbors', 10); I got an error: error: vl_kdtreequery: Unknown option 'NumNeighbors'. Then I read the source code. And I found there are two global variables with the same name 'options' in file 'vl_kdtreequery.c' and 'vl_kdtreebuild.c', which makes the bug. I think you can rename them.

In https://github.com/vlfeat/vlfeat/blob/1b9075fc42fe54b42f0e937f8b9a230d8e2c7701/vl/covdet.c#L2877-L2880

vl_covdet_extract_orientations_for_frame() is called and its return value is not checked, despite the called function's docs:

The function returns @c NULL if memory is insufficient.

Thus vl_covdet_extract_orientations() can silently continue despite allocation failure.

A proper fix requires an API change:

The type signature of vl_covdet_extract_orientations() needs to be changed to be able to report allocation failure, because it calls a function that can fail to allocate.

I suggest that like vl_covdet_put_image(), it should return int with semantics:

The function fails by returing ::VL_ERR_ALLOC if the memory is insufficient.

I found an isseu about sift command. I ran the command sift tmp.pgm --output --output=im0.sift --edge-thresh 10 --peak-thresh 5 --verbose in linux, the size of the output file was always 0 KB. So I have to debug the code, and I found the sift process runs into the following error judging condiction in pgm.c.

  # line 236
  if(! (max_value >= 65536)) {
    return vl_set_last_error(VL_ERR_PGM_INV_META, "Invalid PGM meta information");
  }

the max_value of my tmp.pgm is 255. It means the max grey level of my gray image is 255. So I modify the code as follow and it work. I wonder if this is a mistake.

  # line 236
  if(max_value >= 65536) {
    return vl_set_last_error(VL_ERR_PGM_INV_META, "Invalid PGM meta information");
  }