submitted a bug report against the "linux-kbuild-6.1" package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935536
The report describes a failure of "objtool" command while compiling the
Kernel. Coincidentally when the date of the CPU's microcode was changed
and tha
On 2024-01-10, Herb Garcia wrote:
> Does this method also create the modules?
>> make menuconfig
this one permits you to change kernel parameters if needed
>> make bindeb-pkg
this one compiles kernel and produces
linux-headers-*.deb
linux-image-*.deb
linux-image contains kernel and internal
Does this method also create the modules?
-Herb
On Tue, 2024-01-09 at 13:17 +0100, Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
On 2024-01-09, HP Garcia wrote:
> What dependencies did you install?
All are installed with those commands, thanks Debian :)
apt build-dep linux
apt install build-essential libncurses-dev
(last one for running menuconfig with ncurses)
What dependencies did you install?
~Herb
On Tue, Jan 9, 2024, 7:23 AM Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
> > I d
On 2024-01-08, Herb Garcia wrote:
> I was able to compile Linux kernel 6.1.X.
>
> When I tried compiling kernel 6.5.x and ran into issues.
>
> I download the required dependencies as required per
> https://www.kernel.org/doc/html/v6.7/process/changes.html#changes
To compile 6
I was able to compile Linux kernel 6.1.X.
When I tried compiling kernel 6.5.x and ran into issues.
I download the required dependencies as required per
https://www.kernel.org/doc/html/v6.7/process/changes.html#changes
I'm just looking to see if I missed any steps. Here is the list of
com
I did try to compile the 6.5.12 kernel over the weekend, and I got Makefile
errors, BUT, I applied the 6.5 realtime patch first, so the problem may
have been in the patch, and not in the kernel source itself. I should try
compiling an unpatched 6.5.12 kernel to be sure it's an issue with the
Has anyone else had any issues with compiling a kernel 6.5 and higher?
I was about to compile 6.1.58 without any issues. I did do my research and
downloaded the dependencies outlined here:
https://www.kernel.org/doc/html/latest/admin-guide/README.html
I even looked at the error log and can&#
I have shown the details below. Any advice would be appreciated, thank you.
No advice for compiling, but virtualbox is available in sid, and there
is a repository by virtualbox giving access to the software. You may try
them, it may work (I use virtualbox from sid on testing)
Hello,
Apologies for sending "rich text" of the same email previously. That
was an accident.
Here should be the plain text now.
Due to upstream issues, Virtualbox is not available on bookworm.
I have an urgent business use case, that required virtualbox to be installed
on Debian 12 bookworm, as s
Roberto C. Sánchez writes:
> On Thu, Feb 16, 2023 at 10:37:00AM +0100, Andreas Leha wrote:
>>
>> Dear Tomas,
>>
>> Thanks for the swift reply!
>>
>> OK, then I should do `quilt pop -a` before the second compilation,
>> right?
>>
>> But that leads to another error message:
>>
>
> This can be
On Thu, Feb 16, 2023 at 10:37:00AM +0100, Andreas Leha wrote:
>
> Dear Tomas,
>
> Thanks for the swift reply!
>
> OK, then I should do `quilt pop -a` before the second compilation,
> right?
>
> But that leads to another error message:
>
This can be considered a bug in the package. The idea i
writes:
> On Thu, Feb 16, 2023 at 10:05:54AM +0100, Andreas Leha wrote:
>> Dear all,
>>
>> I am re-compiling xscreensaver.
>>
>> Re-compiling once works fine:
>>
>> apt-get source xscreensaver
>> cd xscreensaver-6.0.6+dfsg1
>
On Thu, Feb 16, 2023 at 10:05:54AM +0100, Andreas Leha wrote:
> Dear all,
>
> I am re-compiling xscreensaver.
>
> Re-compiling once works fine:
>
> apt-get source xscreensaver
> cd xscreensaver-6.0.6+dfsg1
> LANG=C debuild -us -uc
>
>
> R
Dear all,
I am re-compiling xscreensaver.
Re-compiling once works fine:
apt-get source xscreensaver
cd xscreensaver-6.0.6+dfsg1
LANG=C debuild -us -uc
Re-compiling a second time errors out, though:
> LANG=C debuild -us -uc
(skipped lines)
dpkg-source: info: us
I want to thank you again, you pointed me in the right direction, I
found a typo with the version exactly as you pointed to, and now its
happily compiling.
On Sun, 25 Apr 2021 17:40:47 -0400,
Darac Marjal wrote:
>
> [1 ]
> [1.1 ]
>
> On 25/04/2021 20:23, John Covici wrote:
On Sun, 25 Apr 2021 17:40:47 -0400,
Darac Marjal wrote:
>
> [1 ]
> [1.1 ]
Thanksfor your quick response, answers in line.
>
> On 25/04/2021 20:23, John Covici wrote:
> > Hi. In the make bzImage step of compiling linux-source-4.19 I get the
> > following error:
On 25/04/2021 20:23, John Covici wrote:
> Hi. In the make bzImage step of compiling linux-source-4.19 I get the
> following error:
>
> CC arch/x86/hyperv/hv_init.o
> arch/x86/hyperv/hv_init.c: In function ‘hyperv_init’:
> arch/x86/hyperv/hv_init.c:338:52: error: e
Hi. In the make bzImage step of compiling linux-source-4.19 I get the
following error:
CC arch/x86/hyperv/hv_init.o
arch/x86/hyperv/hv_init.c: In function ‘hyperv_init’:
arch/x86/hyperv/hv_init.c:338:52: error: expected expression before
‘,’ token
guest_id = generate_guest_id(0
Hi all,
Is there a 'beaten' path for cross compiling C-programs using GTK3 for
Windows? I found several tutorials which are not working anymore. And
everything I tried lead to a dead end.
Does anyone know about this issue? And can give me a hint how to proceed?
Yes, I have installed
Thanks a lot! That gave me a lead to a typo and that has fixed the
problem.
On Sun, 07 Jun 2020 21:27:56 -0400,
Roberto C. Sánchez wrote:
>
> On Sun, Jun 07, 2020 at 09:23:17PM -0400, John Covici wrote:
> > Hi. I am having problems compiling the current linux-source4.19. I
>
On Sun, Jun 07, 2020 at 09:23:17PM -0400, John Covici wrote:
> Hi. I am having problems compiling the current linux-source4.19. I
> am using the same config file -- just copied to .config, except that I
> had to get rid of the gpg key in the cryptographic api section. I get
> t
Hi. I am having problems compiling the current linux-source4.19. I
am using the same config file -- just copied to .config, except that I
had to get rid of the gpg key in the cryptographic api section. I get
the following error when trying to compile:
CC arch/x86/hyperv/hv_init.o
arch
John Covici wrote:
> I am trying to do something very simple, with the config file supplied
> from Debian, I need to do a make bzImage and possible a make modules,
> how can dI do this? Do I need to change the config in some way in
> order to do this?
be patient and start reading - free means fr
On Mon, 30 Sep 2019 16:47:29 -0400,
deloptes wrote:
>
> John Covici wrote:
>
> > Google did not give me that at all. I am not trying to build a Debian
> > package,just trying to compile the kernel.
>
> Then just do
>
> make deb-pkg
>
> You could read more about the make system used by the ker
John Covici wrote:
> I am doing a straight makebzImage not trying to build a deb package.
> In Debian 9, I could do this with no problem.
Obviously you are trying to build the kernel from debian source. You have to
use the original source, without the debian directory. IF there is debian
director
John Covici wrote:
> Google did not give me that at all. I am not trying to build a Debian
> package,just trying to compile the kernel.
Then just do
make deb-pkg
You could read more about the make system used by the kernel
https://www.kernel.org/doc/html/latest/
or in the directory
$ less R
On Mon, Sep 30, 2019 at 04:20:53PM -0400, John Covici wrote:
> > On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> > > So, how do I turn this off so I can compile the thing?
> >
> > "dpkg-buildpackage -b" considers it a warning and skips it.
> > At least it does so for me.
>
> I am d
On Mon, 30 Sep 2019 16:05:16 -0400,
deloptes wrote:
>
> John Covici wrote:
>
> > debian/certs/debian-uefi-certs.pem
>
> https://wiki.debian.org/BuildADebianKernelPackage
>
> I hope you can read - also find a good search engine - first hit
>
>
Google did not give me that at all. I am not t
On Mon, 30 Sep 2019 16:15:38 -0400,
Reco wrote:
>
> Please do not top post.
>
> On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> > So, how do I turn this off so I can compile the thing?
>
> "dpkg-buildpackage -b" considers it a warning and skips it.
> At least it does so for me.
I
Please do not top post.
On Mon, Sep 30, 2019 at 04:10:27PM -0400, John Covici wrote:
> So, how do I turn this off so I can compile the thing?
"dpkg-buildpackage -b" considers it a warning and skips it.
At least it does so for me.
Reco
So, how do I turn this off so I can compile the thing?
On Mon, 30 Sep 2019 16:02:02 -0400,
Reco wrote:
>
> Hi.
>
> On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote:
> > Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
> >
>
John Covici wrote:
> debian/certs/debian-uefi-certs.pem
https://wiki.debian.org/BuildADebianKernelPackage
I hope you can read - also find a good search engine - first hit
On 2019-09-30 15:46 -0400, John Covici wrote:
> Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
>
> CC kernel/rseq.o
> AR kernel/built-in.a
> make[1]: *** No rule to make target
> 'debian/certs/debian-uefi-certs.pem&#
Hi.
On Mon, Sep 30, 2019 at 03:46:41PM -0400, John Covici wrote:
> Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
>
> CC kernel/rseq.o
> AR kernel/built-in.a
> make[1]: *** No rule to make target
> 'debian/cert
Hi. I am getting an error while compiling the kernel 4.19-0-6-amd64.
CC kernel/rseq.o
AR kernel/built-in.a
make[1]: *** No rule to make target
'debian/certs/debian-uefi-certs.pem', needed by
'certs/x509_certificate_list'. Stop.
What package d
ux source code, or
online here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/objtool/Documentation/stack-validation.txt
Furthermore, it answers accurately to your original question
from the 13th of August:
> compiling the kernel up to Debian 9.x
On 19/08/19 at 21:18, Étienne Mollier wrote:
> Franco Martelli, on 2019-08-19:
>> I was thinking to submit a bug report against gcc-8 package. Now that I
>> have a work around, "bdver1" compiles without warnings, I can say
>> enough, what do you think about?
>
> I don't know, to me it sounds more
Franco Martelli, on 2019-08-19:
> I was thinking to submit a bug report against gcc-8 package. Now that I
> have a work around, "bdver1" compiles without warnings, I can say
> enough, what do you think about?
I don't know, to me it sounds more like little bugs on kernel
side, patches silencing war
I was thinking to submit a bug report against gcc-8 package. Now that I
have a work around, "bdver1" compiles without warnings, I can say
enough, what do you think about?
Best regards
--
Franco Martelli
Franco Martelli, on 2019-08-16:
> On 16/08/19 at 17:22, Étienne Mollier wrote:
[...]
> > Compilers may have good optimization routines to boost the speed
> > of the code in several situations, but in other ones there are
> > trade-offs to take between size and performance of the code. I
> > person
On 16/08/19 at 17:22, Étienne Mollier wrote:
> Bonjour,
>
> Woops, this sounds a bit like I might not have used a very clear
> wording. If I were at your place, I would proceed so; but I
> don't have a Piledriver CPU to do actual testing on my side.
> I'm still stuck with an old K10, not to menti
Bonjour,
Franco Martelli, on 2019-09-14:
> On 13/08/19 at 19:35, Étienne Mollier wrote:
[...]
> > I would do a few tests with a virtual
> > machine supporting bdver2 instructions before going live anyway,
> > and backups stored far away from the machine once testing, and
> > po
On 13/08/19 at 19:35, Étienne Mollier wrote:
> Hi Franco,
>
> I'm not fluent enough in GCC 8 for x86_64 to answer to all the
> various warnings you indicated. Some may be harmless, and some
> may eat your data. I would do a few tests with a virtual
> machine supporting bdver2 instructions before
to:
>
> cflags-$(CONFIG_MK8) += $(call cc-option,-march=bdver2) \
> $(call cc-option,-mtune=bdver2,$(call
> cc-option,-mtune=generic))
>
> compiling the kernel up to Debian 9.x stretch all worked fine but with
> Debian 10 buster I get a lot of warning messages:
[...snipp
) \
$(call cc-option,-mtune=bdver2,$(call
cc-option,-mtune=generic))
compiling the kernel up to Debian 9.x stretch all worked fine but with
Debian 10 buster I get a lot of warning messages:
mm/memory.o: warning: objtool: remap_pfn_range()+0xd5: unsupported
intra-function call
mm/memory.o: warning: objtool
On Sat 27 Apr 2019 at 01:47:53 -0500, Richard Owlett wrote:
> On 04/26/2019 02:25 PM, Darac Marjal wrote:
> >
> Using Buster was my original idea but it's not ready in ways important to
> me. I had been looking for Python3.7 in backports. What snags might I hit
> attempting to use a testing packa
On 04/27/2019 02:45 AM, Curt wrote:
On 2019-04-27, Richard Owlett wrote:
https://packages.debian.org/search?keywords=python3.7
python3.7 is available in testing.
Using Buster was my original idea but it's not ready in ways important
to me. I had been looking for Python3.7 in backports. What
and completely risk-free. Thirty minutes work at most.
Advising on what else is needed to test the beta software is not
possible as the package name is unknown.
I think this ticks all the boxes apart from compiling. But why
bother compiling when someone has done it for you and buster is
as ready for anything as stretch is?
--
Brian.
On 2019-04-27, Richard Owlett wrote:
>>
>> https://packages.debian.org/search?keywords=python3.7
>>
>> python3.7 is available in testing.
>
> Using Buster was my original idea but it's not ready in ways important
> to me. I had been looking for Python3.7 in backports. What snags might I
> hit
On 04/26/2019 09:26 PM, Kushal Kumaran wrote:
Richard Owlett writes:
I wish to try some beta software which assumes python3.7 is
installed. I have Debian 9.8 installed on a machine dedicated to this
exercise. I did a web search and got a half dozen on topic hits. There
were enough differences
On 04/26/2019 02:39 PM, deloptes wrote:
Richard Owlett wrote:
I wish to try some beta software which assumes python3.7 is installed. I
have Debian 9.8 installed on a machine dedicated to this exercise. I did
a web search and got a half dozen on topic hits. There were enough
differences that I w
On 04/26/2019 02:25 PM, Darac Marjal wrote:
On 26/04/2019 18:42, Richard Owlett wrote:
I wish to try some beta software which assumes python3.7 is installed.
I have Debian 9.8 installed on a machine dedicated to this exercise. I
did a web search and got a half dozen on topic hits. There were en
as far as compiling things goes. There were
automatic systems being developed when I was interested, but as far as
I can see, there's no point to LFS if you're just going to push a
button. I did it twice, mainly to learn what I could, with better
understanding the second time, the first tr
Richard Owlett writes:
> I wish to try some beta software which assumes python3.7 is
> installed. I have Debian 9.8 installed on a machine dedicated to this
> exercise. I did a web search and got a half dozen on topic hits. There
> were enough differences that I wasn't sure if I was missing somet
Richard Owlett wrote:
> I wish to try some beta software which assumes python3.7 is installed. I
> have Debian 9.8 installed on a machine dedicated to this exercise. I did
> a web search and got a half dozen on topic hits. There were enough
> differences that I wasn't sure if I was missing somethi
a half dozen on topic hits.
>> There were enough differences that I wasn't sure if I was missing
>> something important. The last time I compiled something was on a PDP
>> 11/45 in approximately 1975.
>>
>>
> You mentioned that you considered LFS. If you have the time
On 26/04/2019 18:42, Richard Owlett wrote:
> I wish to try some beta software which assumes python3.7 is installed.
> I have Debian 9.8 installed on a machine dedicated to this exercise. I
> did a web search and got a half dozen on topic hits. There were enough
> differences that I wasn't sure if
ences that I wasn't sure if I was missing
> something important. The last time I compiled something was on a PDP
> 11/45 in approximately 1975.
>
>
You mentioned that you considered LFS. If you have the time, that's
a real baptism of fire as far as compiling things goes.
On Fri 26 Apr 2019 at 12:42:04 -0500, Richard Owlett wrote:
> I wish to try some beta software
Very informative.
> which assumes python3.7 is installed. I
> have Debian 9.8 installed on a machine dedicated to this exercise. I did a
> web search
For what?
>
I wish to try some beta software which assumes python3.7 is installed. I
have Debian 9.8 installed on a machine dedicated to this exercise. I did
a web search and got a half dozen on topic hits. There were enough
differences that I wasn't sure if I was missing something important. The
last time
Thomas Schmitt wrote:
> Hi,
hello, :)
> songbird's autotools wrote:
^
*snicker*
>> configure: WARNING: sys/ioctl.h: see the Autoconf documentation
>> configure: WARNING: sys/ioctl.h: section "Present But Cannot Be
>
> According to
>
> https://www.gnu.org/s
wrote:
> On Thu, Feb 07, 2019 at 06:06:01AM -0500, songbird wrote:
>> i used to be able to compile my program=20
>> using Debian testing/unstable by setting the -m32
>> in CFLAGS and regenerating my environment.
>>=20
>> now i'm picking up a warning from the auto stuff=20
>> like:
>>=20
>> =3
Hi,
songbird's autotools wrote:
> configure: WARNING: sys/ioctl.h: see the Autoconf documentation
> configure: WARNING: sys/ioctl.h: section "Present But Cannot Be
According to
https://www.gnu.org/software/autoconf/manual/autoconf-2.64/html_node/Present-But-Cannot-Be-Compiled.html
you will
On Thu, Feb 07, 2019 at 06:06:01AM -0500, songbird wrote:
> i used to be able to compile my program
> using Debian testing/unstable by setting the -m32
> in CFLAGS and regenerating my environment.
>
> now i'm picking up a warning from the auto stuff
> like:
>
> =
> checking sys/ioctl.h
i used to be able to compile my program
using Debian testing/unstable by setting the -m32
in CFLAGS and regenerating my environment.
now i'm picking up a warning from the auto stuff
like:
=
checking sys/ioctl.h usability... no
checking sys/ioctl.h presence... yes
configure: WARNING: sys
On Sun, Dec 16, 2018 at 01:52:47AM +, billium wrote:
[...]
> I am having problems with cross compiling a small program for
> the BeagleBone (single board Arm Cortex A processor) on an amd64
> PC. I can compile the program on the BeagleBone, but would like
>
I am having problems with cross compiling a small program for
the BeagleBone (single board Arm Cortex A processor) on an amd64
PC. I can compile the program on the BeagleBone, but would like
to use QTcreator on the Debian Buster desktop PC.
With the
Hello everybody.
I hope someone can help me out of this (hopefully) simple problem.
Currently iam working on a new kernel (4.12.13) for my debian server.
The kernel compiles fine, the initrd will be created using
mkinitramfs -o /boot/initrd.img-4.12.13 4.12.13
but on a reboot and booting wit
Leslie Rhorer wrote:
> I found the issue. The firmware I needed was bnx2x, not bnx2.
Amen!
I found the issue. The firmware I needed was bnx2x, not bnx2.
Well, this seems odd. I don't see any candidate which looks likely, to me, in
/lib/firmware/bnx2:
Backup:/lib/firmware/bnx2# la
total 636
drwxr-xr-x 2 root root 4096 Feb 19 15:20 .
drwxr-xr-x 7 root root 4096 Feb 19 15:20 ..
-rw-r--r-- 1 root root 93172 Jun 15 2014 bnx2-mips-06-5.0.0.j3.fw
Leslie Rhorer wrote:
> It is a stock kernel from the current Debian repository. The firmware was
> loaded using `apt-get install firmware-bnx2`.
Try to find the firmware that matches - I think the message tells you which
version is required. Compare with what you hahve in /lib/firmware
Here in j
It is a stock kernel from the current Debian repository. The firmware was
loaded using `apt-get install firmware-bnx2`.
Leslie Rhorer wrote:
> [ 20.327836] bnx2x :07:00.0: firmware: failed to load
> [ bnx2x/bnx2x-e2-7.8.19.0.fw (-2) 20.327840] bnx2x :07:00.0: Direct
> [ firmware load failed with error -2 20.327842] bnx2x :07:00.0:
> [ Falling back to user helper 20.328247] bnx2x:
> [ [bnx2x_func_hw_init
The motherboard has a built-in Ethernet port.
Backup:/# ip link
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth2: mtu 1500 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether 50:46:5d:65:15:9c brd ff:ff:ff:ff:ff:ff
3: eth0:
It's still not working, but the card is in the udev file, and ifconfig -a shows
the interface. When I try to bring it up, however, it gives me an error:
Backup:/# ifconfig -a
eth0 Link encap:Ethernet HWaddr 0
On Sun, Feb 19, 2017 at 03:54:32AM -0800, Leslie Rhorer wrote:
> I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters. I am not
> finding any pre-built binaries nor a .deb reporitory for these cards, so I am
> attempting t o compile from scratch, but I get the following error during th
Well, that's good to know, but it's not coming up. I've never added an
Ethernet adapter post-install, so I suspect I need to do something, but I am
not sure what. I did an lsmod, and the bnx2x module is loaded, but not being
used. I loaded the firmware, but I get this error during boot:
[
Leslie Rhorer wrote:
> bnx2
https://packages.debian.org/jessie/firmware-bnx2
Leslie Rhorer wrote:
> bnx2
most likely you'll need firmware for it as well
Leslie Rhorer wrote:
> I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters. I am
> not finding any pre-built binaries nor a .deb reporitory for these
> cards, so I am attempting t o compile from scratch,
Why? The bnx2 module is available in the default kernel and should
support those
I purchased a couple of Asus PEB-10G/57811-1S 10G LAN adapters. I am not
finding any pre-built binaries nor a .deb reporitory for these cards, so I am
attempting t o compile from scratch, but I get the following error during the
make operation:
Backup/Server-Main/Temp/netxtreme2-7.10.42/bnx2-2
On Wed, Nov 30, 2016 at 4:52 AM, Davide Anchisi wrote:
> I do have libpoppler-qt5-1:
> dpkg -l libpoppler-qt5-1
> ii libpoppler-qt5-1:amd6 0.26.5-2+deb8u1
> and libpoppler-qt5.so.1: /usr/lib/x86_64-linux-gnu/libpoppler-qt5.so.1
>
> The command to build the package. I first went with:
> a
I do have libpoppler-qt5-1:
dpkg -l libpoppler-qt5-1
ii libpoppler-qt5-1:amd6 0.26.5-2+deb8u1
and libpoppler-qt5.so.1: /usr/lib/x86_64-linux-gnu/libpoppler-qt5.so.1
The command to build the package. I first went with:
apt-get -b source libpoppler64=0.48.0-2
but also tried:
dpkg-build
On Tue, Nov 22, 2016 at 4:52 AM, Davide Anchisi wrote:
> Hi,
>
> I am trying to compile "libpoppler" in Debian Jessie (amd64) from testing
> sources:
> apt-get -b source libpoppler64=0.48.0-2
> I resolved the build dependencies:
> apt-get build-dep libpoppler64=0.48.0-2
>
> The build begin
Hi,
I am trying to compile "libpoppler" in Debian Jessie (amd64) from testing
sources:
apt-get -b source libpoppler64=0.48.0-2
I resolved the build dependencies:
apt-get build-dep libpoppler64=0.48.0-2
The build begins, but stops with an error:
make[1]: entering directory
"/home/davide/d
r can't
compile nut-nutrition or if the fltk GUI isn't on a par with things like CRON-
O-meter.
Questions:
* I seem to remember that there is a way of (before, during, or after)
compiling a software package letting the package manager(s) know for whatever
good that does--well, I guess
On Tue 16 Aug 2016 at 22:45:29 +0100, Lisi Reisz wrote:
[...Snip... The history is in previous mails].
> After a lot more wrong turnings and much agonising, thinking instead of
> panicking (at last!) and retrying:
>
> root@Eros:/home/lisi/Sane-Files# scanimage -L
> device `genesys:libusb:001:00
On Tuesday 16 August 2016 17:27:10 Brian wrote:
> On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote:
> > On Tuesday 16 August 2016 13:49:48 Brian wrote:
> > > Mea culpa. Please see the apt-get manual: build-dep (no "s").
> >
> > Thanks, both. :-)
> >
> > Everything now built, though there was
On Tuesday 16 August 2016 17:27:10 Brian wrote:
> Five .debs are built; only libsane, libsane-common and sane-utils need
> to be installed with 'dpkg -i'.
Ah! I don't know about senior moments. I need a rest, some sleep and a new
brain.
Lisi
On Tue 16 Aug 2016 at 15:39:00 +0100, Lisi Reisz wrote:
> On Tuesday 16 August 2016 13:49:48 Brian wrote:
> >
> > Mea culpa. Please see the apt-get manual: build-dep (no "s").
>
> Thanks, both. :-)
>
> Everything now built, though there was an error at the end:
>
> Now running lintian...
> warn
On Tuesday 16 August 2016 13:49:48 Brian wrote:
> On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote:
> > On Monday 15 August 2016 14:25:58 Brian wrote:
> > > A good guide to backporting is at
> > >
> > >
> > > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> > >
> >
On Tue 16 Aug 2016 at 12:57:50 +0100, Lisi Reisz wrote:
> On Monday 15 August 2016 14:25:58 Brian wrote:
> >
> > A good guide to backporting is at
> >
> > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> >
> > A deb-src line in sources.list for unstable is needed to do
>
Le 16/08/2016 à 13:57, Lisi Reisz a écrit :
> I have got stuck. Only slightly further on than I had already got stuck.
> (apt-get said it wasn't downloading what I had already downloaded!)
>
> root@Eros:/home/lisi/Sane-Files# apt-get build-deps libsane-common/testing
> E: Invalid operation bui
On Monday 15 August 2016 14:25:58 Brian wrote:
> On Mon 15 Aug 2016 at 14:23:36 +0200, didier gaumet wrote:
> > Le 15/08/2016 à 12:42, Lisi Reisz a écrit :
> > > Thanks, didier. That is nice to know.
> > >
> > > So it should be in the up-to-date tar ball, if I were to succeed in
> > > sorting that
On Mon 15 Aug 2016 at 19:05:55 +0100, Lisi Reisz wrote:
> On Monday 15 August 2016 14:25:58 Brian wrote:
> > A good guide to backporting is at
> >
> > https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
> >
> > A deb-src line in sources.list for unstable is needed to do
> >
>
On Monday 15 August 2016 14:25:58 Brian wrote:
> A good guide to backporting is at
>
> https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
>
> A deb-src line in sources.list for unstable is needed to do
>
> apt-get source libsane-common/unstable
>
> Then
>
> apt-get build-
1 - 100 of 3013 matches
Mail list logo
