Slackware This Forum is for the discussion of Slackware Linux.
Notices
Welcome to
LinuxQuestions.org , a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free.
Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please
contact us . If you need to reset your password,
click here .
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a
virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month.
Click here for more info.
11-28-2007, 11:26 PM
#1
LQ Newbie
Registered: Jun 2006
Location: Elk Grove, CA
Distribution: Slackware 12.0
Posts: 27
Rep:
having trouble installing some items
Just installed Slackware 12 yesterday.
first tried installing flash 9 player and when i run it, it says that my glibc is version 2.2 and needs to be higher.
ok can do without flash 9
next tried installing Real player 10... Said i didn't have the correct permissions as SU...
don't like mac anyways.
tried installing fuse. and i got this...
Code:
bash-3.1$ su
Password:
bash-3.1# ./fuse.SlackBuild
fuse-2.7.0/
fuse-2.7.0/doc/
fuse-2.7.0/doc/how-fuse-works
fuse-2.7.0/doc/kernel.txt
fuse-2.7.0/README
fuse-2.7.0/configure.in
fuse-2.7.0/aclocal.m4
fuse-2.7.0/Makefile.am
fuse-2.7.0/Makefile.in
fuse-2.7.0/fuse.pc.in
fuse-2.7.0/configure
fuse-2.7.0/AUTHORS
fuse-2.7.0/COPYING
fuse-2.7.0/COPYING.LIB
fuse-2.7.0/ChangeLog
fuse-2.7.0/INSTALL
fuse-2.7.0/NEWS
fuse-2.7.0/compile
fuse-2.7.0/config.guess
fuse-2.7.0/config.rpath
fuse-2.7.0/config.sub
fuse-2.7.0/depcomp
fuse-2.7.0/install-sh
fuse-2.7.0/ltmain.sh
fuse-2.7.0/missing
fuse-2.7.0/mkinstalldirs
fuse-2.7.0/README.NFS
fuse-2.7.0/Filesystems
fuse-2.7.0/FAQ
fuse-2.7.0/kernel/
fuse-2.7.0/kernel/Makefile.in
fuse-2.7.0/kernel/configure.ac
fuse-2.7.0/kernel/configure
fuse-2.7.0/kernel/config.h.in
fuse-2.7.0/kernel/install-sh
fuse-2.7.0/kernel/dev.c
fuse-2.7.0/kernel/dir.c
fuse-2.7.0/kernel/file.c
fuse-2.7.0/kernel/inode.c
fuse-2.7.0/kernel/fuse_i.h
fuse-2.7.0/kernel/fuse_kernel.h
fuse-2.7.0/kernel/control.c
fuse-2.7.0/include/
fuse-2.7.0/include/old/
fuse-2.7.0/include/old/fuse.h
fuse-2.7.0/include/fuse.h
fuse-2.7.0/include/fuse_compat.h
fuse-2.7.0/include/fuse_common.h
fuse-2.7.0/include/fuse_common_compat.h
fuse-2.7.0/include/fuse_lowlevel.h
fuse-2.7.0/include/fuse_lowlevel_compat.h
fuse-2.7.0/include/fuse_opt.h
fuse-2.7.0/include/ulockmgr.h
fuse-2.7.0/include/fuse_kernel.h
fuse-2.7.0/include/Makefile.am
fuse-2.7.0/include/Makefile.in
fuse-2.7.0/include/config.h.in
fuse-2.7.0/lib/
fuse-2.7.0/lib/Makefile.am
fuse-2.7.0/lib/Makefile.in
fuse-2.7.0/lib/fuse.c
fuse-2.7.0/lib/fuse_i.h
fuse-2.7.0/lib/fuse_kern_chan.c
fuse-2.7.0/lib/fuse_loop.c
fuse-2.7.0/lib/fuse_loop_mt.c
fuse-2.7.0/lib/fuse_lowlevel.c
fuse-2.7.0/lib/fuse_misc.h
fuse-2.7.0/lib/fuse_mt.c
fuse-2.7.0/lib/fuse_opt.c
fuse-2.7.0/lib/fuse_session.c
fuse-2.7.0/lib/fuse_signals.c
fuse-2.7.0/lib/helper.c
fuse-2.7.0/lib/modules/
fuse-2.7.0/lib/modules/subdir.c
fuse-2.7.0/lib/modules/iconv.c
fuse-2.7.0/lib/mount.c
fuse-2.7.0/lib/mount_util.c
fuse-2.7.0/lib/mount_util.h
fuse-2.7.0/lib/mount_bsd.c
fuse-2.7.0/lib/ulockmgr.c
fuse-2.7.0/lib/fuse_versionscript
fuse-2.7.0/util/
fuse-2.7.0/util/Makefile.am
fuse-2.7.0/util/Makefile.in
fuse-2.7.0/util/fusermount.c
fuse-2.7.0/util/mount.fuse.c
fuse-2.7.0/util/ulockmgr_server.c
fuse-2.7.0/util/udev.rules
fuse-2.7.0/util/init_script
fuse-2.7.0/example/
fuse-2.7.0/example/Makefile.am
fuse-2.7.0/example/Makefile.in
fuse-2.7.0/example/fusexmp.c
fuse-2.7.0/example/fusexmp_fh.c
fuse-2.7.0/example/hello.c
fuse-2.7.0/example/hello_ll.c
fuse-2.7.0/example/null.c
checking build system type... i686-pc-linux-gnulibc1
checking host system type... i686-pc-linux-gnulibc1
checking target system type... i686-pc-linux-gnulibc1
checking for a BSD-compatible install... /bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
here is the config.log
Code:
his file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by fuse configure 2.7.0, which was
generated by GNU Autoconf 2.61. Invocation command line was
$ ./configure --prefix=/ --includedir=/usr/include --localstatedir=/var --with-pkgconfigdir=/usr/lib/pkgconfig --enable-lib --enable-util
## --------- ##
## Platform. ##
## --------- ##
hostname = Linux12
uname -m = i686
uname -r = 2.6.21.5-smp
uname -s = Linux
uname -v = #2 SMP Tue Jun 19 14:58:11 CDT 2007
/usr/bin/uname -p = Intel(R) Pentium(R) D CPU 3.00GHz
/bin/uname -X = unknown
/bin/arch = i686
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /sbin
PATH: /usr/sbin
PATH: /bin
PATH: /usr/bin
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1974: checking build system type
configure:1992: result: i686-pc-linux-gnulibc1
configure:2014: checking host system type
configure:2029: result: i686-pc-linux-gnulibc1
configure:2051: checking target system type
configure:2066: result: i686-pc-linux-gnulibc1
configure:2108: checking for a BSD-compatible install
configure:2164: result: /bin/ginstall -c
configure:2175: checking whether build environment is sane
configure:2218: result: yes
configure:2283: checking for gawk
configure:2299: found /bin/gawk
configure:2310: result: gawk
configure:2321: checking whether make sets $(MAKE)
configure:2342: result: yes
configure:2677: checking for style of include used by make
configure:2705: result: GNU
configure:2778: checking for gcc
configure:2794: found /usr/bin/gcc
configure:2805: result: gcc
configure:3043: checking for C compiler version
configure:3050: gcc --version >&5
gcc (GCC) 4.1.2
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3053: $? = 0
configure:3060: gcc -v >&5
Reading specs from /usr/lib/gcc/i486-slackware-linux/4.1.2/specs
Target: i486-slackware-linux
Configured with: ../gcc-4.1.2/configure --prefix=/usr --enable-shared --enable-languages=ada,c,c++,fortran,java,objc --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --with-arch=i486 --target=i486-slackware-linux --host=i486-slackware-linux
Thread model: posix
gcc version 4.1.2
configure:3063: $? = 0
configure:3070: gcc -V >&5
gcc: '-V' option must have argument
configure:3073: $? = 1
configure:3096: checking for C compiler default output file name
configure:3123: gcc -O2 -march=i486 -mtune=i686 conftest.c >&5
/usr/lib/gcc/i486-slackware-linux/4.1.2/../../../../i486-slackware-linux/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:3126: $? = 1
configure:3164: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "fuse"
| #define PACKAGE_TARNAME "fuse"
| #define PACKAGE_VERSION "2.7.0"
| #define PACKAGE_STRING "fuse 2.7.0"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "fuse"
| #define VERSION "2.7.0"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3171: error: C compiler cannot create executables
See `config.log' for more details.
## ---------------- ##
## Cache variables. ##
## ---------------- ##
ac_cv_build=i686-pc-linux-gnulibc1
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-O2 -march=i486 -mtune=i686'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i686-pc-linux-gnulibc1
ac_cv_path_install='/bin/ginstall -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_make_make_set=yes
ac_cv_target=i686-pc-linux-gnulibc1
## ----------------- ##
## Output variables. ##
## ----------------- ##
ACLOCAL='${SHELL} /tmp/SBo/fuse-2.7.0/missing --run aclocal-1.9'
AMDEPBACKSLASH='\'
AMDEP_FALSE='#'
AMDEP_TRUE=''
AMTAR='${SHELL} /tmp/SBo/fuse-2.7.0/missing --run tar'
AR=''
AUTOCONF='${SHELL} /tmp/SBo/fuse-2.7.0/missing --run autoconf'
AUTOHEADER='${SHELL} /tmp/SBo/fuse-2.7.0/missing --run autoheader'
AUTOMAKE='${SHELL} /tmp/SBo/fuse-2.7.0/missing --run automake-1.9'
AWK='gawk'
BSD_FALSE=''
BSD_TRUE=''
CC='gcc'
CCDEPMODE=''
CFLAGS='-O2 -march=i486 -mtune=i686'
CPP=''
CPPFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR='.deps'
DUMPBIN=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
FGREP=''
GREP=''
ICONV_FALSE=''
ICONV_TRUE=''
INIT_D_PATH=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
LD=''
LDFLAGS=''
LIBICONV=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LINUX_FALSE=''
LINUX_TRUE=''
LN_S=''
LTLIBICONV=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /tmp/SBo/fuse-2.7.0/missing --run makeinfo'
MOUNT_FUSE_PATH=''
NM=''
OBJEXT=''
PACKAGE='fuse'
PACKAGE_BUGREPORT=''
PACKAGE_NAME='fuse'
PACKAGE_STRING='fuse 2.7.0'
PACKAGE_TARNAME='fuse'
PACKAGE_VERSION='2.7.0'
PATH_SEPARATOR=':'
RANLIB=''
SED=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
UDEV_RULES_PATH=''
VERSION='2.7.0'
ac_ct_CC='gcc'
ac_ct_DUMPBIN=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include='include'
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnulibc1'
build_alias=''
build_cpu='i686'
build_os='linux-gnulibc1'
build_vendor='pc'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host='i686-pc-linux-gnulibc1'
host_alias=''
host_cpu='i686'
host_os='linux-gnulibc1'
host_vendor='pc'
htmldir='${docdir}'
includedir='/usr/include'
infodir='${datarootdir}/info'
install_sh='/tmp/SBo/fuse-2.7.0/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
libfuse_libs=''
localedir='${datarootdir}/locale'
localstatedir='/var'
lt_ECHO='echo'
mandir='${datarootdir}/man'
mkdir_p='mkdir -p --'
oldincludedir='/usr/include'
pdfdir='${docdir}'
pkgconfigdir=''
prefix='/'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
subdirs2=''
subdirs=''
sysconfdir='${prefix}/etc'
target='i686-pc-linux-gnulibc1'
target_alias=''
target_cpu='i686'
target_os='linux-gnulibc1'
target_vendor='pc'
## ----------- ##
## confdefs.h. ##
## ----------- ##
#define PACKAGE_NAME "fuse"
#define PACKAGE_TARNAME "fuse"
#define PACKAGE_VERSION "2.7.0"
#define PACKAGE_STRING "fuse 2.7.0"
#define PACKAGE_BUGREPORT ""
#define PACKAGE "fuse"
#define VERSION "2.7.0"
configure: exit 77
appreciate any help i can get and thank you.
11-28-2007, 11:51 PM
#2
LQ Newbie
Registered: Jun 2006
Location: Elk Grove, CA
Distribution: Slackware 12.0
Posts: 27
Original Poster
Rep:
Ok sorry about that, did some more searching and was able to find the cause. looks like gcc was not installed so just redownloaded it and just used pkgtool to install and i got flash and fuse to work but still giving me the permission problem with real
Quote:
bash-3.1$ ./RealPlayer10GOLD.bin
bash: ./RealPlayer10GOLD.bin: Permission denied
bash-3.1$ su
Password:
bash-3.1# ./RealPlayer10GOLD.bin
bash: ./RealPlayer10GOLD.bin: Permission denied
bash-3.1#
11-29-2007, 01:25 AM
#3
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
As a first time user, you probably should have installed everything.
Try this:
Code:
sudo chmod 755 RealPlayer10GOLD.bin
./RealPlayer10GOLD.bin
11-29-2007, 03:03 AM
#4
LQ Newbie
Registered: Nov 2007
Location: Poland
Distribution: Slackware, Beton
Posts: 7
Rep:
Also remember to execute this binary on linux FS. This is common mistake that ppl try to change attributes while they keep file on FAT/NTFS
11-29-2007, 09:07 AM
#5
LQ Newbie
Registered: Jun 2006
Location: Elk Grove, CA
Distribution: Slackware 12.0
Posts: 27
Original Poster
Rep:
tried to install everything, popped up with a few errors during the install and didn't know how to go about fixing it.
but i'll give that chmod a try.
and it's all on an ext3 formatted partition.
thanks again.
11-29-2007, 10:19 AM
#6
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep:
Or instead of chmod you can:
sh RealPlayer10GOLD.bin
11-29-2007, 11:54 AM
#7
LQ Newbie
Registered: Jun 2006
Location: Elk Grove, CA
Distribution: Slackware 12.0
Posts: 27
Original Poster
Rep:
so are chmod and sh pretty much the same command? i tried sh last night and it said that permission was denied or that
the file wasn't executable, can't really remember atm.
redownloaded a couple times to make sure it wasn't that.
11-29-2007, 11:57 AM
#8
LQ Newbie
Registered: Jun 2006
Location: Elk Grove, CA
Distribution: Slackware 12.0
Posts: 27
Original Poster
Rep:
i remember more than one item failing durining initial setup of my slack so...
is there a log somewhere of what was installed and not installed (ie failed) initially?
maybe fixing those will help with this.
11-29-2007, 12:13 PM
#9
LQ Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
But then what's the use of realplayer when you have mplayer ?
If you have Slackware 12.0 then flash player 9 will work just fine when installed properly, as long as you have glibc installed.....
11-29-2007, 12:49 PM
#10
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639
Rep:
Quote:
Originally Posted by
dive
Or instead of chmod you can:
sh RealPlayer10GOLD.bin
No, you can't. sh is for executing scripts. As the extension implies, RealPlayer10GOLD.bin is a binary file.
Brian
11-29-2007, 12:53 PM
#11
LQ Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
No, actually you can, because everything in the shell is run by sh (bash in most cases). 'sh *' is equivalent to './*'.
11-29-2007, 12:53 PM
#12
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639
Rep:
Quote:
Originally Posted by
m3lkor001
so are chmod and sh pretty much the same command?
They are very different. chmod allows you to set permissions on files and directories. sh is for running shell scripts. Usually you must make a file executable with chmod in order to run it. Scripts can be run with sh without the need of making them executable.
Brian
11-29-2007, 12:56 PM
#13
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639
Rep:
Quote:
Originally Posted by
H_TeXMeX_H
No, actually you can, because everything in the shell is run by sh (bash in most cases). 'sh *' is equivalent to './*'.
Code:
sh RealPlayer10GOLD.bin
RealPlayer10GOLD.bin: RealPlayer10GOLD.bin: cannot execute binary file
...whereas ./RealPlayer10GOLD.bin runs the program fine.
Brian
11-29-2007, 01:06 PM
#14
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
Imho, you all are not giving the full explanation.
1) sh filename.bin won't work on binary files, but will work on shell scripts which are named with bin extension (usually that's wrong to do, but sometimes it happens when the binary part is incorporated into shell script). Most often you'll get cannot execute binary file error.
2) sh script.sh will work on script which is not executable, because sh will read contents of the script and execute those contents itself. ./script.sh won't work if script is not executable, because when you run ./script.sh another instance of sh (you define what in the header of the script) is instantiated. non-executable script cannot start other programs.
3) if normal binary file is not executable, it cannot be run.
4) to check file type use file file_name
I hope I'm not wrong myself.
11-29-2007, 01:20 PM
#15
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639
Rep:
Quote:
Originally Posted by
Alien_Hominid
1) sh filename.bin won't work on binary files, but will work on shell scripts which are named with bin extension (usually that's wrong to do, but sometimes it happens when the binary part is incorporated into shell script).
That's why I said the extension _implies_ that it is a binary file, it doesn't necessarily mean it is.
Never-the-less, your explanation is more complete and clearer than mine.
Brian
All times are GMT -5. The time now is 02:13 PM .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know .
Latest Threads
LQ News