Hi Chris,
Christopher Lemmer Webber writes:
> Thanks! I got things working by going the tarball route, though
> slightly more indirectly than the approach you suggested here. What I
> did was get the latest release-candidate tarball and list the patches I
> specifically needed in the package
Mark H Weaver writes:
> Hi Chris,
>
> I wrote earlier:
>> My first guess is that '/gnu/store/…-linux-next-…-checkout/include'
>> should not be in the C include path while compiling that file, but that
>> it's getting added. The difference might be due to the fact that the
>> 'source' in this
Hi Chris,
I wrote earlier:
> My first guess is that '/gnu/store/…-linux-next-…-checkout/include'
> should not be in the C include path while compiling that file, but that
> it's getting added. The difference might be due to the fact that the
> 'source' in this case is a directory instead of a
Tobias Geerinckx-Rice wrote:
(add-before 'configure 'fix-CPATH (lambda _;; Temporary
hack to
remove -checkout/include which breaksthings. ;; Why is this
not
necessary when building in a‘guix environment’ ;; and in the
Guix
linux-libre package?Git-checkout-related? (setenv
Chris,
Christopher Lemmer Webber wrote:
Anyone more familiar with the linux build process who can give
me some tips? Especially since I board a plane very early
tomorrow morning :)
My own kernel package has nothing left in common with linux-libre,
but it does build from git and has this
Hi Chris,
Christopher Lemmer Webber writes:
> Unfortunately my laptop was failing and I needed to pick up a new one
> asap before a conference I leave for tomorrow morning, so I bought one
> off the shelf from a retail store. Also unfortunately, while the
> hardware is supported in upstream
Hello,
Unfortunately my laptop was failing and I needed to pick up a new one
asap before a conference I leave for tomorrow morning, so I bought one
off the shelf from a retail store. Also unfortunately, while the
hardware is supported in upstream linux, it isn't in any of the released
tarballs
