Backported versions for Debian 8, 9, & Ubuntu 14.04, 16.04, 16.10, 17.04 in a repo
stevenpusser
Status: Interested
Joined: 14 Jan 2017
Posts: 39
Reply Quote
The latest Liquorix headers require gcc-7, not available except in Debian development or Ubuntu 17.10+. These versions are rebuilt to use the default gcc version for each release.

You can get to the automatically generated instruction page here:

https://software.opensuse.org/download.html?project=home%3Astevenpusser%3Acodelite&package=liquorix

The Ubuntu directions use sudo, the Debian ones say to use root. Debian sudo users can become root with "sudo -i".

Simplifying the Debian Stretch directions:

Add the repo as root:
:: Code ::
echo 'deb http://download.opensuse.org/repositories/home:/stevenpusser:/codelite/Debian_9.0/ /' > /etc/apt/sources.list.d/liquorix.list


Download the key as a standard user:
:: Code ::
wget -nv https://download.opensuse.org/repositories/home:stevenpusser:codelite/Debian_9.0/Release.key -O Release.key


Add the key to your key store and update the package database as root:
:: Code ::
apt-key add - < Release.key
apt-get update


Jessie users can just replace the "9.0" in the instructions with "8.0". Ubuntu user's instruction
with sudo are simpler to follow, just copy and paste into the terminal the instructions from that link for your release.

Ignore the command about "apt-get install liquorix", that's a dummy package I had to add.

64-bit users can then install the kernel and header metapackages:

:: Code ::
apt-get install linux-image-liquorix-amd64 linux-headers-liquorix-amd64


32-bit users can choose between the standard or the PAE versions:

:: Code ::
apt-get install linux-image-liquorix-i686 linux-headers-liquorix-i686


or

:: Code ::
apt-get install linux-image-liquorix-i686-pae linux-headers-liquorix-i686-pae


Jessie users of proprietary drivers and ndiswrapper may need to update to patched or backported versions from this repo to get them to build on the newer kernels.
Back to top
stevenpusser
Status: Interested
Joined: 14 Jan 2017
Posts: 39
Reply Quote
Hmmm--what happens if I replace the versioned version of gcc in debian/config/defines with just "gcc"? Would that then build using the default gcc for each distro release, so I wouldn't have to maintain separate gcc-4.8, 4.9, 5, and 6 versions?
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 711
Reply Quote
Yes, I would suspect that's true. The reason I specify the GCC version is to prevent a newer version of GCC in Debian Unstable / Testing from being used mid-packaging of a kernel. That and I like to watch the latest Ubuntu releases, and once a new stable version of Ubuntu comes out with the newer GCC in the repo, I update the next major version of Liquorix with that.

But yes, there's no harm in just setting the GCC version to "gcc" and building that on an older distribution. In fact, for automated builds among many old distributions (16.04, 16.10, 17.04, 17.10, etc), you'll want to do that anyway and not specify any version in particular.
Back to top
stevenpusser
Status: Interested
Joined: 14 Jan 2017
Posts: 39
Reply Quote
Cool...but should I keep building with -O2 instead of -O3 optimization for gcc < 5? That will still mean two different versions, which is better than the four I'm doing now.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 711
Reply Quote
Hmm, that's a good question. I actually suspect -O3 is much more stable than you might think and is simply less tested only because maintainers are afraid of supporting it. I've been using O3 for quite some time (since 2016-05-16 per the atom feed: https://liquorix.net/atom)

So, I think that's up to you. The newer the version, major or minor, the less likely O3 will have unwanted side effects.

On the other hand, I'm now building official packages for Ubuntu on the PPA here: https://launchpad.net/~damentz/+archive/ubuntu/liquorix

If you check the liquorix-package git repository, I'll now be running a new build script as part of my local build process that sends Ubuntu source packages to launchpad: https://github.com/damentz/liquorix-package/blob/master/scripts/make-ppa-spins.sh

Just a heads up, once this is all stabilized, I'll advertise it on the main website and we probably won't need your backports (except for maybe Debian stable).
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3865
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I"m not sure about that, I see you built for beta, current, and the two previous releases, which means, the pools go back about 1, 1.5 years. This doesn't seem to relate to supporting LTR or Debian Stable releases, which can easily be 2 to 3 to more times older.

It looks to me like the liquorix ppa's will be good for people running the recent releases, but the stuff being done by stevenpusser is focused on the stable stuff that can be older.
Back to top
stevenpusser
Status: Interested
Joined: 14 Jan 2017
Posts: 39
Reply Quote
At least I can cut out the builds that are duplicated in the official PPA now. Looks like I can switch to just one source version now that uses just "gcc" in the defines. I'll try leaving -O3 in there, too.
Back to top
ilu
Status: New User - Welcome
Joined: 01 Nov 2017
Posts: 4
Reply Quote
After using liquorix 4.12 for some time on my debian stretch I now decided to try to upgrade using your repo. What I'm getting is:
:: Code ::
env LC_ALL=C apt upgrade -s
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.9.0-4-amd64 linux-headers-4.9.0-4-common linux-headers-4.9.0-5-amd64 linux-headers-4.9.0-5-common linux-image-4.9.0-4-amd64 linux-image-4.9.0-5-amd64
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
  linux-headers-liquorix-amd64 linux-image-liquorix-amd64
The following packages will be upgraded:
  firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intel-sound
  firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-nonfree
  firmware-misc-nonfree firmware-myricom firmware-netxen firmware-qlogic firmware-realtek firmware-samsung firmware-siano
  firmware-ti-connectivity nvidia-detect
23 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Is that correct? All that firmware but the kernel is still held back?
Back to top
Display posts from previous:   

All times are GMT - 8 Hours