Lighthouse 64 5.14.2 Beta 4

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
meeki
Posts: 122
Joined: Mon 23 Jul 2012, 04:48
Location: Portland OR

#161 Post by meeki »

don570
Note to Tazoc:

Could you convert my right-click package to 64 bit for FATDOG

I don't have a 64 bit computer. It should be easy to make a pet package.

Just remove all .desktop files except one. Then proceed with
making a pet package from a folder. ---> dir2pet

Before the last tar command , put back all .desktop files
If Tazoc does not get it done I'll take care of it.

Just let me know so 2 people are not doing the same thing

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#162 Post by smokey01 »

I think I did this a while back. Check my site.

http://www.smokey01.com/software/Fatdog64-600

gcmartin

#163 Post by gcmartin »

This is NOT about a problem.

But, I can seel where this Slackware repo based 64bit PUP and its extension for Update, management, and communication is going to make a extend LH64 beyond it already great implementation.

Thanks to TaZoC, Smokey01, 01Micko, Meeki, and everyone else who is extending this effort. This is the most comprehensive packaging, OOTB, in this community.

Carry on!!!

User avatar
meeki
Posts: 122
Joined: Mon 23 Jul 2012, 04:48
Location: Portland OR

#164 Post by meeki »

Hal

http://www.freedesktop.org/wiki/Software/hal


any chance of getting this working in LHPUP64?

my amazon movies need it lol

Not high priority as I jsut use VirtualBox for this.

./configure --disable-console-kit --disable-policy-kit
works but make install I get
linux_dvd_rw_utils.c:54:23: fatal error: scsi/scsi.h: No such file or directory
compilation terminated.

Code: Select all

bash-4.1# ./configure --disable-console-kit --disable-policy-kit
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/x86_64-slackware-linux/bin/ld
checking if the linker (/usr/x86_64-slackware-linux/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/x86_64-slackware-linux/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ld used by g++... /usr/x86_64-slackware-linux/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether make sets $(MAKE)... (cached) yes
checking whether ln -s works... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking sys/ioccom.h usability... no
checking sys/ioccom.h presence... no
checking for sys/ioccom.h... no
checking sys/inotify.h usability... yes
checking sys/inotify.h presence... yes
checking for sys/inotify.h... yes
checking for /usr/share/hwdata/pci.ids... no
checking for /usr/share/misc/pci.ids... no
checking for /usr/share/pci.ids... yes
checking for /var/lib/misc/pci.ids... no
configure: WARNING: autodetected pci.ids in /usr/share
checking for /usr/share/hwdata/usb.ids... no
checking for /usr/share/misc/usb.ids... no
checking for /usr/share/usb.ids... yes
checking for /var/lib/misc/usb.ids... no
configure: WARNING: autodetected usb.ids in /usr/share
checking gtk-doc version >= 1.3... yes
checking expat.h usability... yes
checking expat.h presence... yes
checking for expat.h... yes
checking for XML_ParserCreate in -lexpat... yes
checking usb.h usability... yes
checking usb.h presence... yes
checking for usb.h... yes
checking for usb_find_devices in -lusb... yes
checking for SMBIOSFreeMemory in -lsmbios... no
checking pci/pci.h usability... yes
checking pci/pci.h presence... yes
checking for pci/pci.h... yes
checking for pci_init in -lpci... yes
checking for libusb20_dev_get_info in -lusb... no
checking for gperf... /usr/bin/gperf
checking whether to rebuild gperf header files... checking for DBUS... yes
checking for GLIB... yes
checking if GLib is version 2.14.0 or newer... yes
checking for BLKID... yes
checking for pgoff_t... no
checking for BLKGETSIZE64... yes
checking for getgrouplist... yes
checking for asprintf... yes
checking for mallopt... yes
checking for strndup... yes
checking for xmlto... no
checking whether to build DocBook documentation... checking for xmllint... /usr/bin/xmllint
yes
checking for Sony PIC headers... yes
configure: creating ./config.status
config.status: creating hal.pc
config.status: creating hal-storage.pc
config.status: creating hal.conf
config.status: creating Makefile
config.status: creating hald/Makefile
config.status: creating hald/dummy/Makefile
config.status: creating hald/linux/Makefile
config.status: creating hald/linux/probing/Makefile
config.status: creating hald/linux/addons/Makefile
config.status: creating hald/solaris/Makefile
config.status: creating hald/solaris/probing/Makefile
config.status: creating hald/solaris/addons/Makefile
config.status: creating hald/freebsd/Makefile
config.status: creating hald/freebsd/probing/Makefile
config.status: creating hald/freebsd/libprobe/Makefile
config.status: creating hald/freebsd/addons/Makefile
config.status: creating hald-runner/Makefile
config.status: creating libhal/Makefile
config.status: creating libhal-storage/Makefile
config.status: creating tools/Makefile
config.status: creating tools/freebsd/Makefile
config.status: creating tools/linux/Makefile
config.status: creating partutil/Makefile
config.status: creating policy/Makefile
config.status: creating fdi/Makefile
config.status: creating fdi/information/Makefile
config.status: creating fdi/information/10freedesktop/Makefile
config.status: creating fdi/information/20thirdparty/Makefile
config.status: creating fdi/policy/Makefile
config.status: creating fdi/policy/10osvendor/Makefile
config.status: creating fdi/policy/20thirdparty/Makefile
config.status: creating fdi/preprobe/Makefile
config.status: creating fdi/preprobe/10freedesktop/Makefile
config.status: creating fdi/preprobe/20thirdparty/Makefile
config.status: creating doc/Makefile
config.status: creating doc/api/Makefile
config.status: creating doc/api/libhal/Makefile
config.status: creating doc/api/libhal/version.xml
config.status: creating doc/api/libhal-storage/Makefile
config.status: creating doc/api/libhal-storage/version.xml
config.status: creating doc/spec/Makefile
config.status: creating doc/spec/hal-spec.xml.in
config.status: creating doc/man/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

                    HAL 0.5.14
                  ==============

        prefix:                           /usr/local
        libdir:                           ${exec_prefix}/lib
        libexecdir:                       ${exec_prefix}/libexec
        bindir:                           ${exec_prefix}/bin
        sbindir:                          ${exec_prefix}/sbin
        datadir:                          ${datarootdir}
        sysconfdir:                       ${prefix}/etc
        localstatedir:                    ${prefix}/var
        docdir:                           ${datarootdir}/doc/${PACKAGE_TARNAME}
        dbus-1 system.d dir:              ${prefix}/etc/dbus-1/system.d
        pci.ids dir:                      /usr/share
        usb.ids dir:                      /usr/share
	udev prefix:            	  ${exec_prefix}/lib

        compiler:                         gcc
        cflags:                           -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare
        ldflags:                          -Wl,--as-needed 
        cppflags:                         
        xmlto:                            no
        xmllint:                          /usr/bin/xmllint
        User for HAL:                     haldaemon
        Group for HAL:                    haldaemon
        hald pidfile:                     ${prefix}/var/run/hald/pid
        hald socket dir:                  ${prefix}/var/run/hald
        eject program:                    /usr/bin/eject

        OS backend:                       linux

        use acpi kernel interface:        yes
        use acpid interface:              yes
        use libusb:                       no
        use libpci:                       yes
        use libparted:                    no
        use gperf:                        yes
        use PolicyKit:                    no
        use ConsoleKit:                   no
        use ACL management:               no
        use umount.hal helper:            no
        use ACPI:                         yes
        use PMU:                          yes
        use APM:                          yes
        use Sony PIC:                     yes

        Macbook backlight support:        yes (Linux only, x86 only, requires libpci)
        Macbook Pro utils:                yes (Linux only, x86 only, requires libpci)
        iMac backlight support:           yes (Linux only, x86)
        OMAP utils:                       no (Linux only, arm only)
        CPU frequency scaling:            yes (Linux only)
        Re-map multimedia keys:           yes (Linux only, requires gperf)
        Forward IBM ACPI events:          no (Linux only)
        Forward Toshiba ACPI events:      no (Linux only)
	USB wireless mouse power:         no (Linux only, requires libusb)
	Dell Backlight:                   no (Linux only, requires libsmbios >= 0.13.4)

	Support deprecated(removed) keys: no (via a FDI-file)

        Maintainer mode:                  no
        Building verbose mode:            no
        Building api docs:                yes
        Building docs:                    no
        Building man pages:               yes

WARNING: PolicyKit is disabled. You need to manually edit the hal.conf
         file to lock down the service. Failure to do so allows any
         caller to make hald do work on their behalf which may be
         a huge SECURITY HOLE. I repeat: YOU NEED TO EDIT THE FILE
         hal.conf to match your distro/site to avoid NASTY SECURITY HOLES.

NOTE: You have to install init scripts yourself and tweak your own policy

NOTE: Remember to create user haldaemon and group haldaemon before make install

NOTE: For development, use run-hald.sh and debug-hald.sh scripts in hald/ to 
      use programs (callouts, probers, addons) and device information files 
      from build directories. You may still need 'make install' to
      install the udev rule to receive events from udev.

<root> /initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14
bash-4.1# make install
Making install in libhal
make[1]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal'
  CC     libhal.lo
libhal.c: In function 'libhal_property_fill_value_from_variant':
libhal.c:347:2: warning: case value '97' not in enumerated type 'LibHalPropertyType'
  CCLD   libhal.la
make[2]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal'
test -z "/usr/local/lib" || .././install-sh -c -d "/usr/local/lib"
 /bin/sh ../libtool   --mode=install /usr/bin/ginstall -c   libhal.la '/usr/local/lib'
libtool: install: /usr/bin/ginstall -c .libs/libhal.so.1.0.0 /usr/local/lib/libhal.so.1.0.0
libtool: install: (cd /usr/local/lib && { ln -s -f libhal.so.1.0.0 libhal.so.1 || { rm -f libhal.so.1 && ln -s libhal.so.1.0.0 libhal.so.1; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libhal.so.1.0.0 libhal.so || { rm -f libhal.so && ln -s libhal.so.1.0.0 libhal.so; }; })
libtool: install: /usr/bin/ginstall -c .libs/libhal.lai /usr/local/lib/libhal.la
libtool: install: /usr/bin/ginstall -c .libs/libhal.a /usr/local/lib/libhal.a
libtool: install: chmod 644 /usr/local/lib/libhal.a
libtool: install: ranlib /usr/local/lib/libhal.a
libtool: finish: PATH="/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R7/bin:/root/my-applications/bin:/usr/lib64/java/bin:/opt/qt4/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
test -z "/usr/local/include/hal" || .././install-sh -c -d "/usr/local/include/hal"
 /usr/bin/ginstall -c -m 644 libhal.h '/usr/local/include/hal'
make[2]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal'
make[1]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal'
Making install in libhal-storage
make[1]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal-storage'
  CC     libhal-storage.lo
libhal-storage.c: In function 'libhal_storage_policy_set_icon_mapping':
libhal-storage.c:132:3: warning: 'libhal_storage_policy_set_icon_path' is deprecated (declared at libhal-storage.c:101)
libhal-storage.c: In function 'libhal_drive_policy_compute_display_name':
libhal-storage.c:217:3: warning: 'libhal_volume_policy_compute_size_as_string' is deprecated (declared at libhal-storage.c:157)
libhal-storage.c: In function 'libhal_volume_policy_compute_display_name':
libhal-storage.c:365:2: warning: 'libhal_volume_policy_compute_size_as_string' is deprecated (declared at libhal-storage.c:157)
libhal-storage.c: In function 'libhal_drive_policy_compute_icon_name':
libhal-storage.c:544:3: warning: 'libhal_storage_policy_lookup_icon' is deprecated (declared at libhal-storage.c:137)
libhal-storage.c:548:3: warning: 'libhal_storage_policy_lookup_icon' is deprecated (declared at libhal-storage.c:137)
libhal-storage.c: In function 'libhal_volume_policy_compute_icon_name':
libhal-storage.c:569:3: warning: 'libhal_storage_policy_lookup_icon' is deprecated (declared at libhal-storage.c:137)
libhal-storage.c:574:3: warning: 'libhal_storage_policy_lookup_icon' is deprecated (declared at libhal-storage.c:137)
libhal-storage.c:587:3: warning: 'libhal_storage_policy_lookup_icon' is deprecated (declared at libhal-storage.c:137)
libhal-storage.c:591:3: warning: 'libhal_storage_policy_lookup_icon' is deprecated (declared at libhal-storage.c:137)
  CCLD   libhal-storage.la
make[2]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal-storage'
test -z "/usr/local/lib" || .././install-sh -c -d "/usr/local/lib"
 /bin/sh ../libtool   --mode=install /usr/bin/ginstall -c   libhal-storage.la '/usr/local/lib'
libtool: install: warning: relinking `libhal-storage.la'
libtool: install: (cd /initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal-storage; /bin/sh /initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libtool  --silent --tag CC --mode=relink gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -version-info 1:0:0 -Wl,--as-needed -o libhal-storage.la -rpath /usr/local/lib libhal-storage.lo -ldbus-1 -lpthread -lrt ../libhal/libhal.la )
libtool: install: /usr/bin/ginstall -c .libs/libhal-storage.so.1.0.0T /usr/local/lib/libhal-storage.so.1.0.0
libtool: install: (cd /usr/local/lib && { ln -s -f libhal-storage.so.1.0.0 libhal-storage.so.1 || { rm -f libhal-storage.so.1 && ln -s libhal-storage.so.1.0.0 libhal-storage.so.1; }; })
libtool: install: (cd /usr/local/lib && { ln -s -f libhal-storage.so.1.0.0 libhal-storage.so || { rm -f libhal-storage.so && ln -s libhal-storage.so.1.0.0 libhal-storage.so; }; })
libtool: install: /usr/bin/ginstall -c .libs/libhal-storage.lai /usr/local/lib/libhal-storage.la
libtool: install: /usr/bin/ginstall -c .libs/libhal-storage.a /usr/local/lib/libhal-storage.a
libtool: install: chmod 644 /usr/local/lib/libhal-storage.a
libtool: install: ranlib /usr/local/lib/libhal-storage.a
libtool: finish: PATH="/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/X11R7/bin:/root/my-applications/bin:/usr/lib64/java/bin:/opt/qt4/bin:/sbin" ldconfig -n /usr/local/lib
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,-rpath -Wl,LIBDIR' linker flag
   - have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
test -z "/usr/local/include/hal" || .././install-sh -c -d "/usr/local/include/hal"
 /usr/bin/ginstall -c -m 644 libhal-storage.h '/usr/local/include/hal'
make[2]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal-storage'
make[1]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/libhal-storage'
Making install in partutil
make[1]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/partutil'
  CC     partutil.lo
  CC     logger.lo
  CCLD   libpartutil.la
make[2]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/partutil'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/partutil'
make[1]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/partutil'
Making install in hald
make[1]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald'
make  install-recursive
make[2]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald'
Making install in dummy
make[3]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/dummy'
  CC     osspec.lo
  CCLD   libhald_dummy.la
make[4]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/dummy'
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
make[4]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/dummy'
make[3]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/dummy'
Making install in freebsd
make[3]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd'
Making install in libprobe
make[4]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/libprobe'
make[5]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/libprobe'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/libprobe'
make[4]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/libprobe'
Making install in probing
make[4]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/probing'
make[5]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/probing'
test -z "/usr/local/libexec" || ../../.././install-sh -c -d "/usr/local/libexec"
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/probing'
make[4]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/probing'
Making install in addons
make[4]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/addons'
make[5]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/addons'
test -z "/usr/local/libexec" || ../../.././install-sh -c -d "/usr/local/libexec"
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/addons'
make[4]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd/addons'
Making install in .
make[4]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd'
make[5]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd'
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd'
make[4]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd'
make[3]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/freebsd'
Making install in linux
make[3]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/linux'
Making install in probing
make[4]: Entering directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/linux/probing'
  CC     probe-input.o
  CC     logger.o
  CCLD   hald-probe-input
  CC     probe-hiddev.o
  CCLD   hald-probe-hiddev
  CC     probe-storage.o
  CC     linux_dvd_rw_utils.o
linux_dvd_rw_utils.c:54:23: fatal error: scsi/scsi.h: No such file or directory
compilation terminated.
make[4]: *** [linux_dvd_rw_utils.o] Error 1
make[4]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/linux/probing'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald/linux'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14/hald'
make: *** [install-recursive] Error 1
<root> /initrd/mnt/dev_save/Download/a/extracted-tgz/hal-0.5.14

User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

hal-0.5.14-x86_64-3.pet (testing only)

#165 Post by tazoc »

meeki wrote:Hal
http://www.freedesktop.org/wiki/Software/hal

any chance of getting this working in LHPUP64?

my amazon movies need it lol

Not high priority as I jsut use VirtualBox for this.

./configure --disable-console-kit --disable-policy-kit
works but make install I get
linux_dvd_rw_utils.c:54:23: fatal error: scsi/scsi.h: No such file or directory
compilation terminated.
[/code]
Try this Pet: http://www.lhpup.org/update/L64-514/Sys ... 6_64-3.pet

I adapted it for LH64 from a couple of Slackware64 packages at
http://slackware.cs.utah.edu/pub/slackw ... kware64/l/
and included the missing scsi.h at /usr/include/scsi/. (Will also add scsi.h to the next devX.)

Hope that helps,
TaZoC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#166 Post by don570 »

To meeki


You're the only person that has ever expressed any desire
to make a right click package :)

Be careful how you name the package.

I suggest rightclick-fatdog-1.0.pet

or

rightclick-64bit-1.0.pet


Don

_____________________________________

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#167 Post by smokey01 »


User avatar
tazoc
Posts: 1157
Joined: Mon 11 Dec 2006, 08:07
Location: Lower Columbia Basin WA US
Contact:

#168 Post by tazoc »

smokey01 wrote:Don570, already done it here.
http://www.smokey01.com/software/Fatdog ... -5.9.8.pet
Thank you smokey01, I haven't had a chance to look at that. :D

I think some mimetypes in Lighthouse64 might differ from other Pups, but if so, and you haven't already, Meeki might be able to tweak the Pet.

Regards,
TaZoC
[url=http://www.lhpup.org/][b][size=100]lhpup.org[/size][/b] [img]http://www.lhpup.org/gallery/images/favicon.png[/img][/url] [url=http://www.lhpup.org/release-lhp.htm#602]Lighthouse 64 6.02[/url]

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#169 Post by smokey01 »

tazoc wrote:
smokey01 wrote:Don570, already done it here.
http://www.smokey01.com/software/Fatdog ... -5.9.8.pet
Thank you smokey01, I haven't had a chance to look at that. :D

I think some mimetypes in Lighthouse64 might differ from other Pups, but if so, and you haven't already, Meeki might be able to tweak the Pet.

Regards,
TaZoC
tazoc they differ in Fatdog too but every right click app I have tried works so far. There are bound to be some that don't.
Last edited by smokey01 on Thu 20 Sep 2012, 08:40, edited 1 time in total.

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#170 Post by don570 »

I originally got the scripts and apps out of Lighthouse 32 bit and
some from Fluppy

____________________________________________________

User avatar
meeki
Posts: 122
Joined: Mon 23 Jul 2012, 04:48
Location: Portland OR

#171 Post by meeki »

I'll test smokeys 1st on SAT then if any issue I'll build yours :)

I got burnt out with pet tweaking after Skype. I'm back to my self again.

My latest fun has been trying to get amazon videos working in LH64. thanks to tazoc getting me HAL im onto flash plugin issue. It now wants to work but as soon as it loads the vid it crashes the plugin to the amazon video and any other webpage open using flash.

I have a feeling this may be as bad a skype pet :( Its fun fig this stuff out though.

Puppyt
Posts: 907
Joined: Fri 09 May 2008, 23:37
Location: Moorooka, Queensland
Contact:

#172 Post by Puppyt »

Hi TaZoC and other puppy gurus,
we love LH64 here - last few weeks have forgotten that we ever used MicroSoft OS's this baby has been rock-solid and such a pleasure to use. Thank You!

Now this morning I broke the system trying to get our (last working) scanner operational in LH64. Must have loaded the wrong package from the slackware repos and on reboot, lost the human interface peripherals of USB mouse and PS2 keyboard. Managed to replace the broken LH64save.3fs from an earlier snap2 backup (and make a habit of moving all my working files off-home anyway) so I've spent about a day trying to nut out sane, hplip and parport issues with HP backends under LH64 - but I feel like I'm tilting at windmills. Xsane doesn't look for parallel port scanners (nor peasyscan), hplip-slacko-5.3.3 pet doesn't seem to be functional here, and I don't have a clue about installing ppscsi - should I actually need it to communicate with the scanner. I first installed hplip_scan_fd64 -3.11.5 but I dunno that the 5100C is supported. Any suggestions on the matter will be gratefully received - but I am thinking that a parallel-usb port adapter might be the sanest way to go,
Cheers
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#173 Post by rcrsn51 »

Puppyt wrote:I first installed hplip_scan_fd64 -3.11.5 but I dunno that the 5100C is supported.
It's not. According to the README here, you will need a lot of stuff to get this relic working. And it may not work at all with new kernels.
Any suggestions on the matter will be gratefully received - but I am thinking that a parallel-usb port adapter might be the sanest way to go.
An adapter won't make it work. Go to your local thrift store and buy an old HP or Canon multi-function unit. Check that the ink cartridges are still inside, even if they are dried up. The scanner unit will probably work fine.

Send your 5100C to the recycler.

Puppyt
Posts: 907
Joined: Fri 09 May 2008, 23:37
Location: Moorooka, Queensland
Contact:

#174 Post by Puppyt »

Heh - thanks rcrsn51 ;)

I *might* try to get it working under WINE. We have generally pretty poor recycling options out here in rural Australia, and generally it winds up as landfill despite Council's claims to the contrary. My trouble is I've since bought (new) a CanoScan3000 and a HP ScanJet G2400 and both died in the *rs* very soon after purchase. The Disposable Mentality infuriates me... but so does the scan speed of the old beast. So I am in partial agreement with you - this dinosaur isn't worth any more time recompiling for 64-bit, Linux 3.0.3 kernel environs, particularly by a numpty like me.
Ho hum - might have to do my scanning from my old Toshie 3480CT - it still has an XP partition on it somewheres for just such contingencies. There's blood and electrons to be squeezed from these old stones yet...
Thanks for the heads up on the adapter issue.
Cheers
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...

User avatar
meeki
Posts: 122
Joined: Mon 23 Jul 2012, 04:48
Location: Portland OR

Python Programming

#175 Post by meeki »

So I needed to do some python coding. Have not done this out of windowsXP so I fig what they hey I know the Devx-LH64_514.sfs has let me run all my python stuff.

Typed in idle in terminal and got;
" ** IDLE can't import Tkinter. Your Python may not be configured for Tk. ** "
Well I know i can do it in a text editor but rather missed IDLE Python GUI.

after much poking around It only needs tcl and tk http://www.tcl.tk/software/tcltk/
"export LD_LIBRARY_PATH="
and a putting it all in a sfs keeps it away from the current lib links. With out it python cant find them.

Made an icon in the utility/Development menu and some checks.

Code: Select all

#!/bin/bash

export LD_LIBRARY_PATH=/usr/local/lib

file="/usr/lib64/python2.6/site-packages/scripts/idle"
if [ -e "$file" ]
then
	idle
else
	zenity --warning --text "Unable to load IDLE\!\nFirst check that you have installed and are running the Devx-L64_514.sfs\n If Devx is installed feel free to contact meeki007@gmail.com to report an error." --title "LH64 IDLE warning"
fi
Install the Python-IDLE_tcl_tk-LH64-8.5.12.sfs and enjoy the stock Python IDE for your own code projects.

Download Link to the SFS 3.2meg
http://dl.dropbox.com/u/12968946/lighth ... 8.5.12.sfs




:)

User avatar
Q5sys
Posts: 1105
Joined: Thu 11 Dec 2008, 19:49
Contact:

#176 Post by Q5sys »

TazOC,
Was catching up on some reading on Barry's Blog and I found this post about PPM: http://bkhome.org/blog/?viewDetailed=02985

Will those changes be able to get worked into the final LH64 release that you said you were working on? I personally dont need it, but I do think it would help those less skilled in Linux. Since you're release is already so user friendly, I was hoping it'd get added (if you had time).

Update: I'll be working on the new XFCE for LHP64 later tonight... hopefully things will go smoothly. :)

EDIT: You told me before but Im daft and forgot... what is the dir in LHP that shows all the installed packages? The one where each package has a corresponding file identifying it.

User avatar
meeki
Posts: 122
Joined: Mon 23 Jul 2012, 04:48
Location: Portland OR

LHPUP Record

#177 Post by meeki »

TazOC and every one else.

I too have been working on a program for LHPUP for a long time now. Its close to Release.

LHPUP Record

Screen capture GUI for FFMPEG. The GUI has a bit more to go but most of the bash hacks are done.

>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<

Video of what i'm trying to do.
http://youtu.be/9bwOAV_tvvo

>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<

I have not forgot you Puppyt

A while back you asked for some howto's on setting up lighthouse as a samba / web / server for hosting things.

I took this to heart and decided to do some stuff by recoding my desktop screen with audio and making some howto vids.

The Sad/Bad:
puppy for sure and linux in general does not have any real nice programs for this.

Recodmydesktop
http://recordmydesktop.sourceforge.net/about.php

Loved it in linux mint or unbuntu, but when i compiled it for light house or puppy its supper slow as hell. tried all the tricks still slow. and it was not fun to make a pet of.
Recordmydektop also saves files as a ogg. You tube hates this format so you have to take the extra step of converting it and this required another program I had to make a pet of.

VLC media player can be found as a sfs for light house

I could never get this to work right as a screen recorder in LHpup

XVidCap
http://sourceforge.net/apps/mediawiki/x ... ?title=Faq

It worked. Lacks tons of features and would not grab my audio from mic. Its captures a nice vid but I got tired of recording my audio separate and then merging them with ffmpeg. yep built a pet of this too for LH64 but I dont relese pets that are a pain to use.

Pup record made by Lobster (you may know him for his macpup videos)
http://www.murga-linux.com/puppy/viewto ... 519#613319

This neet simple script brought my mind into using ffmpeg as a desktop recorder. It worked and was EZ to use but you can only record your entire screen with it. But it made me take a closer look at FFmpeg

So this had lead to:
LHpupRecord

Its far from done but it should work with all Puppy's 4 and up as its all built using SH / BASH Scrips and a few C files that build on install of the pet.

Instead of modding pups I'm stepping into the world as a pup maker.

Puppyt
Posts: 907
Joined: Fri 09 May 2008, 23:37
Location: Moorooka, Queensland
Contact:

#178 Post by Puppyt »

Thanks meeki!
writing in haste due to work/study/family commitments, but I thank you very much for looking into the issue of using LH64 for noob-friendly server functions. My immediate goals have shifted a little since then, but I wonder whether you (or others) might look into at some stage in the future compiling pets for "Openshot", JabRef and the latest "Docear"? Actually, your planned screencasts with LHPUPREC could be especially useful in showing just how a typical compile is performed, and an SFS or PET then generated...

JUST SAW YOUR YOUTUBE - LHPUP RECORD LOOKS FABULOUS! I've muddled about with avidemux, openshot, open movie, handbrake and videodub, and only briefly with screenCapture and simpleSHOT (the latter 2 in pemasu's Exprimo 5x14) so I appreciate the extra miles you've put in to this, and with gtkdialog. I'm sure it will be a real asset to the Puppy fold,
3 CHEERS!
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...

User avatar
meeki
Posts: 122
Joined: Mon 23 Jul 2012, 04:48
Location: Portland OR

PET Building

#179 Post by meeki »

Puppyt

Well got tired of working on the LHPUP Record. Decided to make your video request for building a pet / sfs and make one of your requested apps in the process.
----------------------------------------------------------------------------------------------------------------
Docear
PET
http://dl.dropbox.com/u/12968946/lighth ... ild123.pet
MD5
http://dl.dropbox.com/u/12968946/lighth ... 23.pet.md5


Docear
SFS
http://dl.dropbox.com/u/12968946/lighth ... ild123.sfs
MD5
http://dl.dropbox.com/u/12968946/lighth ... 23.sfs.md5

-----------------------------------------------------------------------------------------------------------------

Docear JAVA to a PET or SFS Tutorial

Video 1 - 31 min
http://youtu.be/H5Qv_ktjIZc

Video 2 - 4 min
http://youtu.be/KLcCcsDVz9M


Puppyt
Posts: 907
Joined: Fri 09 May 2008, 23:37
Location: Moorooka, Queensland
Contact:

#180 Post by Puppyt »

Hey meeki -
just got back from a birthday dinner out for my daughter, practically to find that all *my* birthdays have come at once! Thank you so much for the effort that you've put into LHPUPrecord - I've just downloaded both your pet compilation 'tubes for intense review material on some of my pet projects... I've actually been bleating about such a video instructional resource, elsewhere on the forums (Newbies threads) for ages - this will be a huge help and lift my confidence to actually DIY rather than pester the likes of your Good Self. Thanks especially for burning the midnight oil on this, it's marvelous work. Will give feedback also on the 64-bit/LH Docear SFS later - you've got the absolute latest build there - I've gotta tell Joran and the guys there about that long startup splash - happens in every Puppy I test, but not Windblows - so it isn't the speed of your computer.
Kudos!

(P.S. Just been trying to explain to the wife the significance of your input here, within the broader context of what makes the Puppy Linux Community such a great place to hang around in :) )
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...

Post Reply