configure: error: C preprocessor /lib/cpp fails sanity check

discuss compiling applications for Puppy
Post Reply
Message
Author
belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

configure: error: C preprocessor /lib/cpp fails sanity check

#1 Post by belham2 »

Hi all,

Trying to compile the redshift source program to see if it will work in Peebee's Slacko LxPupSc-17.01.1R. Here is the output I am getting, and I cannot---despiute hours of Googling to find a remedy---get passed this:

"configure: error: C preprocessor /lib/cpp fails sanity check"

Here is the complete terminal output I get from the moment I enter the "./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var" command:

Code: Select all

# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
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 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 gcc option to accept ISO C99... none needed
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/i586-slackware-linux/bin/ld
checking if the linker (/usr/i586-slackware-linux/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for X11... yes
checking for XF86VM... yes
checking for XCB... yes
checking for XCB_RANDR... yes
checking for a Python interpreter with version >= 2.4... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.7/site-packages
checking whether to enable RANDR method... yes
checking whether to enable VidMode method... yes
checking whether to enable GTK status icon... yes
checking how to run the C preprocessor... /lib/cpp
configure: error: in `/root/XXcompiling/redshift-1.2-source-for-building':
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
# 


Anyone have any hints, help, tips or whatever to get pas tthis? Usually this error is because g++ is not installed. Well, in LxPupSc-17.01.1R, the latest g++ (which is gcc-g++-5.40) is already installed. So..?????

User avatar
OscarTalks
Posts: 2196
Joined: Mon 06 Feb 2012, 00:58
Location: London, England

#2 Post by OscarTalks »

What source code package is this?
redshift-1.11 source code, running configure in Dpup Wheezy completes OK with a different response on that line about
"checking how to run the C preprocessor"

Code: Select all

# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
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 make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
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 gcc option to accept ISO C99... -std=gnu99
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc -std=gnu99... /usr/bin/ld
checking if the linker (/usr/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 how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for ANSI C header files... yes
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 for objdir... .libs
checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no
checking for gcc -std=gnu99 option to produce PIC... -fPIC -DPIC
checking if gcc -std=gnu99 PIC flag -fPIC -DPIC works... yes
checking if gcc -std=gnu99 static flag -static works... yes
checking if gcc -std=gnu99 supports -c -o file.o... yes
checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes
checking whether the gcc -std=gnu99 linker (/usr/bin/ld) 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 gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking whether NLS is requested... yes
checking for intltool >= 0.50... 0.50.2 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.14.2
checking for XML::Parser... ok
checking whether Objective C compiler works... no
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for msgmerge... (cached) /usr/bin/msgmerge
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DRM... yes
checking for X11... yes
checking for XF86VM... yes
checking for XCB... yes
checking for XCB_RANDR... no
checking for GLIB... yes
checking for GEOCLUE... no
checking for GEOCLUE2... yes
checking ApplicationServices/ApplicationServices.h usability... no
checking ApplicationServices/ApplicationServices.h presence... no
checking for ApplicationServices/ApplicationServices.h... no
checking whether CoreLocation/CoreLocation.h is usable... no Objective C compiler available
checking windows.h usability... no
checking windows.h presence... no
checking for windows.h... no
checking for a Python interpreter with version >= 3.2... none
checking whether to enable DRM method... yes
checking whether to enable RANDR method... missing dependencies
checking whether to enable VidMode method... yes
checking whether to enable Quartz method... missing dependencies
checking whether to enable WinGDI method... missing dependencies
checking whether to enable Geoclue location provider... missing dependencies
checking whether to enable Geoclue2 location provider... yes
checking whether to enable CoreLocation method... missing dependencies
checking whether to enable GUI status icon... missing dependencies
checking whether to enable Ubuntu icons... no
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking Directory to install systemd user unit files... not enabled
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for stdint.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking for uint16_t... yes
checking for library containing clock_gettime... -lrt
checking for library containing floor... -lm
checking for setlocale... yes
checking for strchr... yes
checking for floor... yes
checking for pow... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating po/Makefile.in
config.status: creating src/Makefile
config.status: creating src/redshift-gtk/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
config.status: executing po/stamp-it commands

 redshift 1.11

    prefix:		/usr
    compiler:		gcc -std=gnu99
    cflags:		-g -O2
    ldflags:		

    Adjustment methods:
    DRM:		yes
    RANDR:		no
    VidMode:		yes
    Quartz (OSX):	no
    WinGDI (Windows):	no

    Location providers:
    Geoclue:		no
    Geoclue2:		yes
    CoreLocation (OSX)	no

    GUI:		no
    Ubuntu icons:	no
    systemd units:	no 

#
Oscar in England
Image

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Re: configure: error: C preprocessor /lib/cpp fails sanity check

#3 Post by Billtoo »

belham2 wrote: Anyone have any hints, help, tips or whatever to get pas tthis? Usually this error is because g++ is not installed. Well, in LxPupSc-17.01.1R, the latest g++ (which is gcc-g++-5.40) is already installed. So..?????
Source code for version 1.8 is available here:

https://slackbuilds.org

It compiled in SlaQ with this:

./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=/usr/lib64 --enable-gui

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#4 Post by belham2 »

Hi Oscar and Billtoo,

Sorry for the late reply....the source package I am using is "Redshift-1.2-source-for-building", downloaded from the slackbuilds.uk. In Barry's SlaQ, I didn't even have to compile anything as the "redshift-1.8-X86_64-1_ejt.txz" package installed and ran no problems. It too I got direct from the Slackbuilds website (UK).

Let me try's billtoo's download link and see if it is/was the same source package I downloaded from slackbuilds.org.uk


Thanks again. I'll report back in a bit here.

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#5 Post by belham2 »

belham2 wrote:Hi Oscar and Billtoo,

Sorry for the late reply....the source package I am using is "Redshift-1.2-source-for-building", downloaded from the slackbuilds.uk. In Barry's SlaQ, I didn't even have to compile anything as the "redshift-1.8-X86_64-1_ejt.txz" package installed and ran no problems. It too I got direct from the Slackbuilds website (UK).

Let me try's billtoo's download link and see if it is/was the same source package I downloaded from slackbuilds.org.uk


Thanks again. I'll report back in a bit here.

Nope,

Downloaded again from Bill's link. It just won't compile in Peebee's LxPupSc-17.01.23R with devx. Stops with the exact same output error message as noted above. And, yes, the build for this download is definitely the 1.8.


I guess I can try to compile it in BarryK's Slaq, but I don't think it will do any good, will it? Barry is using a diff kernel. And it's no use ot compile it in Micko's Slacko 32 because Peebee basically takes all of Micko's builds and just customizes it. So the result would the same, right? I don't know. I need some guidance from you guys here :(

Bill, if it is possible and if you get the chance and/or time, is the redshift build you did small enough to attach to a file to Murga here as a gz file or something, that I could then download? If so, my eyes & me thank you very much in advance... :wink:


P.S. Also, I should note that I just tried the redshift 1.2 build. It too failed at exactly the same output error in the terminal with same messages.

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#6 Post by Billtoo »

belham2 wrote:
Bill, if it is possible and if you get the chance and/or time, is the redshift build you did small enough to attach to a file to Murga here as a gz file or something, that I could then download? If so, my eyes & me thank you very much in advance... :wink:
Is there a 32bit ready made file at SlackBuilds.uk like the 64bit one that you are using in SlaQ?

Have you asked peebee about the problem? I'm not sure but I think there is some header file missing from the devx.

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#7 Post by belham2 »

Billtoo wrote:
belham2 wrote:
Bill, if it is possible and if you get the chance and/or time, is the redshift build you did small enough to attach to a file to Murga here as a gz file or something, that I could then download? If so, my eyes & me thank you very much in advance... :wink:
Is there a 32bit ready made file at SlackBuilds.uk like the 64bit one that you are using in SlaQ?

Have you asked peebee about the problem? I'm not sure but I think there is some header file missing from the devx.

Hi Bill,

A long while back I asked Peebee about redshift, and he wasn't sure & said he didn't really know as he had never dealt with for his creations. The reason I thought it was possible over the past few weeks was reading a comment from the both the author of Redshift and also comments from our SFR (on murga here) where they said the redshift source build file should work for either 32/64 bit when compiling. I'm not sure how that works out. Let me find that redshift thread from a few years back on murga here where SFR was talking about the 32/64 bit & redshift. It's entirely possible I am all screwy in the head remembering what he wrote and what I've read. :oops: Thanks again.

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#8 Post by Billtoo »

belham2 wrote:
Hi Bill,

A long while back I asked Peebee about redshift, and he wasn't sure & said he didn't really know as he had never dealt with for his creations. The reason I thought it was possible over the past few weeks was reading a comment from the both the author of Redshift and also comments from our SFR (on murga here) where they said the redshift source build file should work for either 32/64 bit when compiling. I'm not sure how that works out. Let me find that redshift thread from a few years back on murga here where SFR was talking about the 32/64 bit & redshift. It's entirely possible I am all screwy in the head remembering what he wrote and what I've read. :oops: Thanks again.
I think the problem is with the devx in lxpupsc, could be wrong but there was a problem with it before.

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#9 Post by belham2 »

Billtoo wrote:
belham2 wrote:
Hi Bill,

A long while back I asked Peebee about redshift, and he wasn't sure & said he didn't really know as he had never dealt with for his creations. The reason I thought it was possible over the past few weeks was reading a comment from the both the author of Redshift and also comments from our SFR (on murga here) where they said the redshift source build file should work for either 32/64 bit when compiling. I'm not sure how that works out. Let me find that redshift thread from a few years back on murga here where SFR was talking about the 32/64 bit & redshift. It's entirely possible I am all screwy in the head remembering what he wrote and what I've read. :oops: Thanks again.
I think the problem is with the devx in lxpupsc, could be wrong but there was a problem with it before.

Hi again bill,

Yup, I do believe you are right. I downloaded both of Micko's Slacko 32 (his latest 6.9.6.4) and redshift compiled easily & ran well. Then I took what Micko's compiled and transferred it all to Peebee's latest 32-bit Slacko (LxPupSc.17.01.23R), and it still would not run.

So, not only does redshift not compile in Peebee's, it also won't run what is compiled and works in micko's 32-bit. I know Peebee's is based off of Micko's, but equally I know micko is using python 2.6 and peebee is using python 2.7. Perhaps that has something to do with it too.

It stinks, I have really come to rely on redshift, and I do like Peebee's creations a bit more than micko's, mainly because of the many fine touches he puts in that saves me a lot of time doing it myself. Wish Peebee would maybe re-consider visiting the redshift issue again and making it work & available for his LxPupSc creations.

I can't be the only person with monitor-sensitive eyes using Peebee's stuff? :wink:


Thanks for posting so quickly and helping out today!

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#10 Post by peebee »

You need to install some kernel headers - 01Micko's advice to me was that these should be the headers from the base system where all the libraries had been compiled - so no I don't include them in the devx.....nor the kernel sources for the kernel in LxPupSc (I provide a separate sfs)....

You can get the kernel headers from:
http://slackware.uk/slackware/slackware ... ackware/d/

e.g. currently: kernel-headers-4.4.38_smp-x86-1.txz
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#11 Post by belham2 »

peebee wrote:You need to install some kernel headers - 01Micko's advice to me was that these should be the headers from the base system where all the libraries had been compiled - so no I don't include them in the devx.....nor the kernel sources for the kernel in LxPupSc (I provide a separate sfs)....

You can get the kernel headers from:
http://slackware.uk/slackware/slackware ... ackware/d/

e.g. currently: kernel-headers-4.4.38_smp-x86-1.txz

Hi Peebee,

Gave it a whirl, it didn't matter. Even with the kernel-headers properly installed to "/usr/include", once the terminal gets through "./configure", and you try to run "make", you're faced with a fatal error that is again related to overall libc(s) missing from the devx and/or OS itself. Below is a pic. (I also wanted to note that gnupg, a kind of important program for users to have at their disposal, is failing completely to install/run in LxPupSc versions, yet Micko's 32-bit runs it no problems as well as Barry's Slaq and Slackware in general---this needs attention, as gnupg is how we users stay secure when downloading & verifying and thus building/compiling/making stuff):
Attachments
Redshift-compile-still-fails-even-with-headers-loaded.png
(249.82 KiB) Downloaded 617 times

User avatar
Keef
Posts: 987
Joined: Thu 20 Dec 2007, 22:12
Location: Staffordshire

#12 Post by Keef »

belham2

Not usually an LXpup user but thought I'd give this a go. Got a bit pee'd off with the devx problems so just tried the RedshiftGUI pet I've used before.
It works.
Attachments
Screenshot.jpg
(22.62 KiB) Downloaded 587 times

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#13 Post by belham2 »

Keef wrote:belham2

Not usually an LXpup user but thought I'd give this a go. Got a bit pee'd off with the devx problems so just tried the RedshiftGUI pet I've used before.
It works.
Keef,

I may be a monkey;s uncle, but I can guarantee you redshift does not work in LxPupSc. Just because it installs (like in your pic, which I've done at least 30 times) doesn't mean it works. Try it, you can't adjust brightness, you can't adjust thermal, gamma or anything. The program is neutered because LxPupSc is missing critical stuff that redshift needs to work. I installed the very same thing you did (I am initmately familiar with redshift-build packages and what's on github). In LxPupSc, it ain't happening. There's a difference between something installing and something working...believe me, I almost fell for it too when it first installed like that, and I thought "woohooo", it installed and works. It doesn't :wink:

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#14 Post by Billtoo »

belham2 wrote:
Keef wrote:belham2

Not usually an LXpup user but thought I'd give this a go. Got a bit pee'd off with the devx problems so just tried the RedshiftGUI pet I've used before.
It works.
Keef,

I may be a monkey;s uncle, but I can guarantee you redshift does not work in LxPupSc. Just because it installs (like in your pic, which I've done at least 30 times) doesn't mean it works. Try it, you can't adjust brightness, you can't adjust thermal, gamma or anything. The program is neutered because LxPupSc is missing critical stuff that redshift needs to work. I installed the very same thing you did (I am initmately familiar with redshift-build packages and what's on github). In LxPupSc, it ain't happening. There's a difference between something installing and something working...believe me, I almost fell for it too when it first installed like that, and I thought "woohooo", it installed and works. It doesn't :wink:
Hi,

I installed it in my Gecko-Linux xfce4 install, it autostarts and there is an icon in the tray.
It definately works, almost looks like Barry's Quirky theme :)

I thought it was working in lxpupsc but after seeing the Gecko version it's definately not, must have been the placebo effect.
Attachments
Screenshot.jpg
(16.41 KiB) Downloaded 593 times

User avatar
Keef
Posts: 987
Joined: Thu 20 Dec 2007, 22:12
Location: Staffordshire

#15 Post by Keef »

Brightness definitely works, and the temp settings respond too. Preview does the business as well.

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#16 Post by belham2 »

Keef wrote:Brightness definitely works, and the temp settings respond too. Preview does the business as well.
Keef,

Jesus, instead of saying it works, post what redshift you are using. P.S. I spoke to the developer...it does not work on LxPupSc latest releases. Period. Whatever your using must be something custom, because nothing that is existing in Slackware, Slackbuilds, github or on Puppy boards or any of the other redhsift builds (on the net anywhere) work. They've all been tested. I am not trying to pick an argument, but this has been thoroughly vetted and tested. Post some facts, not gibberish. If you have somehow miraculously coded your own redshift, please do tell, and please post the link. Don't just say you have an "old .pet lying" around. All the old .pets and current new .pets from the last few years in existence have been tested by more than a handful of people--the developer (Jon) included---trying to get them to work on LxPupSc! Conclusion, through mutliple testing---it cannot work because LxPupSC doesn't have the ability (because of what is missing out of the kernel and drivers) to set gamma settings, or brightness settings, or the whole frigging gambit of what redshift is coded for. Post something, anything, then we'll talk, and I'll zip it off to Jon and see what he says. Unreal :roll:

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#17 Post by peebee »

belham2 wrote:I downloaded both of Micko's Slacko 32 (his latest 6.9.6.4) and redshift compiled easily & ran well. Then I took what Micko's compiled and transferred it all to Peebee's latest 32-bit Slacko (LxPupSc.17.01.23R), and it still would not run.
The thing to do therefore, is to replace the LxPupSc kernel with the one from Slacko32-6.9.6.4 (just replace the vmlinuz and zdrv files - renaming the zdrv appropriately) and then try the redshift build you have made.

The woof-ce builds of LxPupSc and Slacko32-6.9.6.4 are almost identical so it must be a kernel issue.....I would think :?
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#18 Post by Billtoo »

I think I got it.

I compiled the newest source code (redshift-1.11.tar.xz) and made a pet
of it.
After installing the pet I click on run in the puppy menu and enter
redshift -l 00.0:-00.00 -t 5500K:3500K (put the latitube and longitude
of your location in place of the zeros)

It's showing up in Task Manager along with a noticable change in the
screen.
Attachments
redshift-1.11-i686.pet
(97.97 KiB) Downloaded 536 times
taskmanager.jpg
(59.8 KiB) Downloaded 450 times

belham2
Posts: 1715
Joined: Mon 15 Aug 2016, 22:47

#19 Post by belham2 »

Billtoo wrote:I think I got it.

I compiled the newest source code (redshift-1.11.tar.xz) and made a pet
of it.
After installing the pet I click on run in the puppy menu and enter
redshift -l 00.0:-00.00 -t 5500K:3500K (put the latitube and longitude
of your location in place of the zeros)

It's showing up in Task Manager along with a noticable change in the
screen.

Bill,

Sent you a PM. I (and two others) tried repeatedly to install your .pet and get it to work in LxPupSc. It would install, but just like our compiling creations, would not run. This was tried on both Intel and AMD motherboards, where redshift runs in nearly all other pups (I personally have about 14 pup and pup-related OSes I am constantly testing). I know Keef and you have it working, but this is now a complete mystery how it is failing on not only several of my machines (5 to be exact), but it also failed ro run on others machines.

Thank you to Keef and you for keeping this alive (seriously appreciate it because I do really like Peebee's creations). And thank you for compiling your version. This has me totally stumped...especially when I've compiled and ran redshift so much, for so long, and many other machines, and never had a problem on one of my setups. But knowing my two other friends, with completely different setups, also again failed with redshift, tells me something is out of my hands here.

Thanks again, guys! :wink:

Post Reply