Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 02 Sep 2014, 09:00
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
Lighthouse 64 5.14.2 Beta 4
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 11 of 17 [255 Posts]   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12, 13, 14, 15, 16, 17 Next
Author Message
meeki


Joined: 23 Jul 2012
Posts: 123
Location: Portland OR

PostPosted: Sat 08 Sep 2012, 02:28    Post subject: Skype 4 !  

Hey every one Looks like I got Skype all sorted out. Its a combination of Slackware libs, Crunch Bang fix etc. Basically others in the Linux community did all the hard work I just parted it together for us and fix some depends and a window wrapper issue.

If you have a bug let me know PLZ but as of now ive been running it for 3 weeks and now only 1 week with out issue. I feel its safe for release.

Skype 4.0.0.7
Skype-LH64-4.0.0.7.pet
http://dl.dropbox.com/u/12968946/lighthouse/skype-LH64-4.0.0.7.pet

Checksum
Skype-LH64-4.0.0.7.pet.md5
http://dl.dropbox.com/u/12968946/lighthouse/skype-LH64-4.0.0.7.pet.md5


Notes:

If you get a bug when you click the chat window all you have to do is move it once and it stays fixed. Right click the bottom of the chat window and select move. Then with out clicking move your mouse towards the bottom right of your screen and the container will stay around it for now on.



Up next - fix drop box. I think i have it fig out with LD_PRELOAD=

[/img]

Last edited by meeki on Sat 08 Sep 2012, 02:49; edited 1 time in total
Back to top
View user's profile Send private message 
meeki


Joined: 23 Jul 2012
Posts: 123
Location: Portland OR

PostPosted: Sat 08 Sep 2012, 02:44    Post subject: Thanks tazoc  

great work tazoc.

Great to hear your doing better.

About donating. I agree times are hard I have not donated much myself.

Its not all about the amount you donate. Your time and knowledge can go a long way supporting the Linux OS you use.

If you fix something, compile something because its not in the pets/sfs/etc. POST IT! odds are someone else needs it too.

Its this awesome community of basic enthusiasts to coding experts (not me Razz ) that keep something like this alive and well.

Keep pecking every one!
Back to top
View user's profile Send private message 
Q5sys


Joined: 11 Dec 2008
Posts: 1048

PostPosted: Sat 08 Sep 2012, 14:59    Post subject: Re: Donations, RC plans  

tazoc wrote:
I have received a total of $66 from 5 contributors year-to-date. I try to acknowledge donations in a timely fashion via PM or email and very much appreciate each one, regardless of the amount. I realize these difficult economic times limit our budgets.

Thats it? That's going to have to be remedied. Expect something in the next few weeks. Smile

tazoc wrote:
My health is not 100% but am able to get something done most days. I am working toward a release candidate ISO of Lighthouse64, with some bug fixes and a few new packages.

Mind a few requests? Only worry about them if you have time.
1) Slightly newer Kernel
2) Slightly newer Glibc version

There are 2 other things I think would be amazing, but I know will take time. I'm willing to compensate you for your time. So they could be paying side projects when you have time to work on them.
1) KDE 4.9 would be epic.
2) If Im unable to make gnome3.4 work with LHP, then I'd be willing to drop some $ to make it happen.

I'm still trying to work on getting gnome ported over to lighthouse but I cant seem to manage it. I've gotten some help from one of the other guys in the forum, but I cant get gnome3 to load and run for more than 30 seconds before crashing to a halt.

So if I continue to hit a roadblock with that I'm going to see about cranking out the 4.1 version of XFCE and the latest LXDE apps.

_________________



My PC is for sale
Back to top
View user's profile Send private message 
meeki


Joined: 23 Jul 2012
Posts: 123
Location: Portland OR

PostPosted: Sun 09 Sep 2012, 14:15    Post subject: Glade 3.82
Subject description: A GUI for makin GUI's
 

Hey thought id share the pet.

Glade is "A User Interface Designer" (http://glade.gnome.org/).

"What is Glade?

Glade is a RAD tool to enable quick & easy development of user interfaces for the GTK+ toolkit and the GNOME desktop environment.

The user interfaces designed in Glade are saved as XML, and by using the GtkBuilder GTK+ object these can be loaded by applications dynamically as needed.

By using GtkBuilder, Glade XML files can be used in numerous programming languages including C, C++, C#, Vala, Java, Perl, Python,and others." (http://glade.gnome.org/)



I like it because you can also insert little bash scripts or bash programs. Make a button and point it to a SH but it can do allot more than that! I like it for making a GUI for all the command line code or scrips I write.

The pet is for GTK+2 ( i think LightHouse is using GTK+3 ) so it should work up the version changes.

Here is a tutorial I found that give you a quick Idea of what your using it for
http://youtu.be/3JuvSobjMi4

Why you should use this while using GTK dialog for writing a GUI for bash commands in Puppy:
for the most part you can avoid compiling constraints. If you write it to work in puppy its going to work most the time for all puppys. If its not working its because your calling a program that is not installed on that puppy but its EZ to write a check in SH file to see if its installed and then send a Dialog to the user to install that program.

Glade pet
Glade-LH64-3.8.2.pet
http://dl.dropbox.com/u/12968946/lighthouse/Glade-LH64-3.8.2.pet


meeki
Back to top
View user's profile Send private message 
tazoc


Joined: 11 Dec 2006
Posts: 1157
Location: Lower Columbia Basin WA US

PostPosted: Thu 13 Sep 2012, 15:39    Post subject: NLS support; Re: Kernel, glibc, KDE4, Gnome  

Request to all contributors: If you get something compiled, before posting, please don't forget the NLS (Native Language Support) files, often found at /usr/share/locales. (Instead of typing make install, type: new2dir make install, then in Step 3, use option 3. This makes it easy to separate them out so that en_US users don't need to download them, while others can.) I really want to make Lighthouse as user-friendly as possible, regardless of locale or native tongue. Even though I've often neglected language support in prior releases, it is now important to me!

Translators can help also. I plan to work on incorporating NLS tools like MoManager in the future.

Thank you for your consideration.

Q5sys wrote:
Mind a few requests? Only worry about them if you have time.
1) Slightly newer Kernel
2) Slightly newer Glibc version
I would like these also, however it's been a long time since last Beta release, so I want to get this 5.15 RC/final out without extensive core changes before working on another Alpha/Beta. The current L64 5.1x aligns with glibc-2.13 from Slackware64 13.37 for improved compatibility with their repos.
Quote:
There are 2 other things I think would be amazing, but I know will take time. I'm willing to compensate you for your time. So they could be paying side projects when you have time to work on them.
1) KDE 4.9 would be epic.
2) If Im unable to make gnome3.4 work with LHP, then I'd be willing to drop some $ to make it happen. I'm still trying to work on getting gnome ported over to lighthouse but I cant seem to manage it. I've gotten some help from one of the other guys in the forum, but I cant get gnome3 to load and run for more than 30 seconds before crashing to a halt.
1) I plan to update KDE for L64 6.xx later. It will likely need glibc-2.15 as well as Qt-4.8.2 and other core updates. Slackware64 14.0 final with glibc-2.15 is getting closer to a release, and that will help me with the latest KDE4 for L64 6.xx later on.
2) Gnome has some vexing dependencies and I couldn't even get Gnome-Games-3.0.1.1 to work properly in L64! I'm afraid I won't be much help with that request.
Quote:
So if I continue to hit a roadblock with that I'm going to see about cranking out the 4.1 version of XFCE and the latest LXDE apps.
Sounds good. I appreciate the assistance, Q5sys. Very Happy

Thanks again,
TaZoC

_________________
lhpup.org Lighthouse 64 6.02
Back to top
View user's profile Send private message Visit poster's website 
tazoc


Joined: 11 Dec 2006
Posts: 1157
Location: Lower Columbia Basin WA US

PostPosted: Thu 13 Sep 2012, 16:04    Post subject: Re: Glade 3.82
Subject description: A GUI for makin GUI's
 

meeki wrote:
The pet is for GTK+2 ( i think LightHouse is using GTK+3 ) so it should work up the version changes....
Glade pet
Glade-LH64-3.8.2.pet
http://dl.dropbox.com/u/12968946/lighthouse/Glade-LH64-3.8.2.pet

meeki
Thank you! I will try this out. The L64 devX has glade-3 --version 3.6.7. Do you have the newer binary? I couldn't find it in the Pet.

L64 5.1x base includes gtk+2-2.24. Most apps use that, although Gvfs-1.8.1-x86_64.sfs adds gtk+3-3.0.9, used by the included gnome-disk-utility.

-TaZoC

_________________
lhpup.org Lighthouse 64 6.02
Back to top
View user's profile Send private message Visit poster's website 
meeki


Joined: 23 Jul 2012
Posts: 123
Location: Portland OR

PostPosted: Thu 13 Sep 2012, 16:31    Post subject:  

NLS

I can do this for now on. I understand the goal and its worth while!
Any new pets from me if they have native lang in the original prog I'll pack it.

As for my current project im codding in C. Id be happy to make NLS support but the task is huge. file menus and things like that are EZ but all the expiation pop outs and the howdo stuff / about would be hard as hell to do.

Are you saying to just use google translate for my CSV file and hope for the best ?
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 3261
Location: Ontario

PostPosted: Thu 13 Sep 2012, 17:30    Post subject:  

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

_____________________________________________________


RSH has written a useful right click to split large files like ISO


http://www.murga-linux.com/puppy/viewtopic.php?t=80872

____________________________________________________
Back to top
View user's profile Send private message 
tazoc


Joined: 11 Dec 2006
Posts: 1157
Location: Lower Columbia Basin WA US

PostPosted: Thu 13 Sep 2012, 17:43    Post subject: NLS support, Google translate  

meeki wrote:
As for my current project im codding in C. Id be happy to make NLS support but the task is huge. file menus and things like that are EZ but all the expiation pop outs and the howdo stuff / about would be hard as hell to do.

Are you saying to just use google translate for my CSV file and hope for the best ?
Good question. I thought about that, not sure how reliable it would be and then there's the question of which and how many languages to support? I noticed Slacko often provides a button to open the GUI text with defaultbrowser to do the same.

I agree, localizing custom apps from scratch is time consuming and probably best accomplished with help of translators familiar with the software, as well as their native linguistics. I was primarily asking to include NLS files that are compiled with apps already.

I am trying to use text entry boxes for Help dialogs, like this from /usr/sbin/sys-info, using gtkdialog:
Code:
TEXT_HELP="\n $APPNAMECAP gathers configuration data from many sources--all into
 one file, to help you get 'under the hood' and track down any problems.
 The report is designed to shed some light on the inner workings of
 $DISTRO_NAME, however the log messages are often cryptic, sometimes
 even alarming. Not to worry--many of the warnings are inconsequential.\n\n
...
 $APPNAME is based on the original report-video by Barry Kauler - bkhome.org"
...
  <edit editable=\"false\">
    <width>620</width><height>350</height>
     <default>\"$(echo -e "$TEXT_HELP" | sed '/./,/^$/!d')\"</default>
   </edit>
so that a user might copy and paste the text into Google translate or whatever means they prefer. (The sed -i '/./,/^$/!d' strips consecutive blank lines, allows 0 blanks at top, 1 at EOF.) I didn't use that with the main GUI because edit/entry boxes don't seem to support markup text with font colors, bold, etc. That's where the 'Google button' might be better.

But this is all still pretty new to me and I have more research to do to. Smile

Thanks for the feedback,
TaZoC

_________________
lhpup.org Lighthouse 64 6.02
Back to top
View user's profile Send private message Visit poster's website 
meeki


Joined: 23 Jul 2012
Posts: 123
Location: Portland OR

PostPosted: Fri 14 Sep 2012, 02:25    Post subject:  

tazoc
Question about Glade pet build:
Quote:
Do you have the newer binary? I couldn't find it in the Pet.

No its the old binary.
Also
'm not running any of the updates you put out on my build Save. I'm a bad guy Razz
I'm updating my LHPUP build now.

tazoc
Quote:
Answer to my translation question.
user might copy and paste the text into Google translate or whatever means they prefer.

I like this option!

tazoc
Quote:
sed -i '/./,/^$/!d'


LOL i such a nublet sed wold have saved me so much time vs my grep and ${string_var//\item_in_string/\replacement_item}

The linux learning curve is strait up for me ATM[/quote]
Back to top
View user's profile Send private message 
meeki


Joined: 23 Jul 2012
Posts: 123
Location: Portland OR

PostPosted: Fri 14 Sep 2012, 02:51    Post subject:  

don570
Quote:
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
Back to top
View user's profile Send private message 
smokey01


Joined: 30 Dec 2006
Posts: 1806
Location: South Australia

PostPosted: Fri 14 Sep 2012, 03:10    Post subject:  

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

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

_________________
Puppy Software <-> Distros <-> Puppy Linux Tips
Back to top
View user's profile Send private message Visit poster's website 
gcmartin

Joined: 14 Oct 2005
Posts: 4238
Location: Earth

PostPosted: Fri 14 Sep 2012, 11:32    Post subject:  

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!!!

_________________
Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engine or use DogPile
Back to top
View user's profile Send private message 
meeki


Joined: 23 Jul 2012
Posts: 123
Location: Portland OR

PostPosted: Mon 17 Sep 2012, 03:52    Post subject:  

Hal
[url]
http://www.freedesktop.org/wiki/Software/hal[/url]

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:
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
Back to top
View user's profile Send private message 
tazoc


Joined: 11 Dec 2006
Posts: 1157
Location: Lower Columbia Basin WA US

PostPosted: Mon 17 Sep 2012, 16:47    Post subject: hal-0.5.14-x86_64-3.pet (testing only)
Subject description: 64-bit HAL Hardware Abstraction Layer
 

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/System/hal-0.5.14-x86_64-3.pet

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

Hope that helps,
TaZoC

_________________
lhpup.org Lighthouse 64 6.02
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 11 of 17 [255 Posts]   Goto page: Previous 1, 2, 3, ..., 9, 10, 11, 12, 13, 14, 15, 16, 17 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2206s ][ Queries: 13 (0.0090s) ][ GZIP on ]