On Monday 25 January 2021 15:32:19 Greg Wooledge wrote: > On Mon, Jan 25, 2021 at 03:13:55PM -0500, Gene Heskett wrote: > > Why Greg, do you seem to always blame the messenger? > > Because the message is ripped up into pieces, and you're telling us > only some half-remembered piece of it. > > > direct copy/paste from the opencv build instructions html page: > > > > wget -O opencv.zip > > https://github.com/opencv/opencv/archive/master.zip wget -O > > opencv_contrib.zip > > https://github.com/opencv/opencv_contrib/archive/master.zip > > Those look safe enough to rule out the URL quoting issue. It would > be nice if you would show us the terminal session in which you ran the > command and got an error. Lacking that information, we can only guess > as to the many possible causes of the many possible errors. > > Here is a short list of guesses. > > 1) You have a shell function or alias that overrides the wget command. > Diagnose this by running "type wget". > Interesting: gene@coyote:~/src/build$ type wget wget is hashed (/usr/bin/wget) gene@coyote:~/src/build$
What the heck does that mean? no extra charge: file /usr/bin/wget /usr/bin/wget: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=35ceae6f53de184f4f46494aa6bb872a6edb0010, stripped > 2) You do not have write permission on the current directory. > Diagnose this by running "id" and "ls -ld .". gene@coyote:~/src/build$ id uid=1000(gene) gid=1000(gene) groups=1000(gene),4(adm),5(tty),6(disk),7 (lp),8(mail),12(man),20(dialout),24(cdrom),25(floppy),27(sudo),29 (audio),33(www-data),44(video),46(plugdev),50(staff),100(users),102 (systemd-timesync),116(lpadmin),118(pulse),119(pulse-access),120 (scanner),122(colord),123(saned),125(nut) gene@coyote:~/src/build$ ls -ld drwxr-xr-x 19 gene gene 4096 Jan 25 14:05 . > The string "Permission denied" in the command's output would be a > strong indicator of this one. I don't recall seeing that go by. > 3) You pasted the command from a source that has non-breaking spaces > or other non-ASCII garbage polluting the arguments. How would that be diagnosed? > 4) You have run out of disk space. > Diagnose this by running "df .". > The string "No space left on device" would strongly indicate this > one. 1T drive, not likely. df -h grep sda /dev/sda5 1.8T 291G 1.4T 18% / /dev/sda1 922M 183M 677M 22% /boot /dev/sda3 46G 4.7G 39G 11% /var > > 5) Quotas. Diagnostic for that? Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
