Advice needed on gcc error

Advice needed on gcc error

[Saul Hazledine]

Hello,
   I installed guix 0.8 into a virtual machine and I hit a problem which 
might be user error or a bug. I thought this would be the right mailing 
list to get help - apologies if it isn't.

I have a running installation of guix/gnu os and wanted to install vim:
   guix package -i vim

I am not using hydra and so the package manager went ahead and tried to 
download and compile the internet (which is what I wanted because I am 
experimenting with the OS). I hit what could be a compilation error in 
gcc 4.8.3:
    Makefile:3584: recipe for target 's-attrtab' failed

This led me to the reason I am contacting the list. A newly installed 
guix machine is pretty basic and does not seem to have any way I report 
a bug from the build other than typing it myself - am I missing a more 
convenient method.

Thanks in advance for any help with the gcc error or the "how to report 
a problem" error.

Saul Hazledine

Re: Advice needed on gcc error

[Ludovic Courtès]

Saul Hazledine <saul@alienscience.org.uk> skribis:

> I have a running installation of guix/gnu os and wanted to install vim:
>   guix package -i vim
>
> I am not using hydra and so the package manager went ahead and tried
> to download and compile the internet (which is what I wanted because I
> am experimenting with the OS). I hit what could be a compilation error
> in gcc 4.8.3:
>    Makefile:3584: recipe for target 's-attrtab' failed

Could you post, say, the last 200 lines of its build log?  One way to
find it is to run:

  ls -lrt /var/log/guix/drvs/*/*gcc-4.8.3*

and then open the most recent one.

> This led me to the reason I am contacting the list. A newly installed
> guix machine is pretty basic and does not seem to have any way I
> report a bug from the build other than typing it myself - am I missing
> a more convenient method.

There’s no convenient method to report build issues, but I agree it
would be very useful.  Something like a --report option to ‘guix build’
that would automatically email bug-guix@gnu.org with the relevant info
upon failure.

Thanks,
Ludo’.

Re: Advice needed on gcc error

[Saul Hazledine]

Hello Ludo,

On 21/11/14 10:21, Ludovic Courtès wrote:
> Could you post, say, the last 200 lines of its build log?  One way to
> find it is to run:
>
>    ls -lrt /var/log/guix/drvs/*/*gcc-4.8.3*
>
> and then open the most recent one.
>

Thank you very much for your offer of help. I have the problem that I 
cannot login to the machine over ssh to get the log file. I have 
installed both openssh and lsh (using hydra) but I cannot find an ssh 
daemon.

I have also added (use-modules (gnu services ssh)) to /etc/config.scm 
and ran  'guix system reconfigure' but no ssh daemon is started.

I totally understand if you do not want to take up time trying to solve 
newbie errors. However, my hope is that these problems provide useful 
information for guix development.

Many thanks
Saul

Re: Advice needed on gcc error

[Ludovic Courtès]

Saul Hazledine <saul@alienscience.org.uk> skribis:

> Thank you very much for your offer of help. I have the problem that I
> cannot login to the machine over ssh to get the log file. I have
> installed both openssh and lsh (using hydra) but I cannot find an ssh
> daemon.
>
> I have also added (use-modules (gnu services ssh)) to /etc/config.scm
> and ran  'guix system reconfigure' but no ssh daemon is started.

You need to add a call to ‘lsh-service’ in the ‘services’ field of the
configuration, similar to what is shown at
<http://www.gnu.org/software/guix/manual/guix.html#Using-the-Configuration-System>.

Also, ATM it is necessary to reboot after ‘reconfigure’ for new services
to be started (that limitation will be removed hopefully soon.)

> I totally understand if you do not want to take up time trying to
> solve newbie errors. However, my hope is that these problems provide
> useful information for guix development.

It’s definitely useful!

Thanks,
Ludo’.

Re: Advice needed on gcc error

[Adam Pribyl]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1878 bytes --]

On Sat, 22 Nov 2014, Ludovic Courtès wrote:

> Saul Hazledine <saul@alienscience.org.uk> skribis:
>
>> Thank you very much for your offer of help. I have the problem that I
>> cannot login to the machine over ssh to get the log file. I have
>> installed both openssh and lsh (using hydra) but I cannot find an ssh
>> daemon.
>>
>> I have also added (use-modules (gnu services ssh)) to /etc/config.scm
>> and ran  'guix system reconfigure' but no ssh daemon is started.
>
> You need to add a call to ‘lsh-service’ in the ‘services’ field of the
> configuration, similar to what is shown at
> 
<http://www.gnu.org/software/guix/manual/guix.html#Using-the-Configuration-System>.
>
> Also, ATM it is necessary to reboot after ‘reconfigure’ for new services
> to be started (that limitation will be removed hopefully soon.)

This is exactly the same thing I am triing to achieve. But the lsh-service
(ssh-daemon) has a dependency on the networking service, which I am not
able to provide - this is the reason why I did add also a
dhcp-client-service, but it seems to not work, as there is no network even
after reconfigure and reboot.

deco status dmd
Started: (nscd file-system-/dev/shm dmd host-name term-tty1 loopback
guix-daemon console-font-tty1 root-file-system user-unmount term-tty4
term-tty5 udev term-tty6 term-tty2 term-tty3 user-processes
console-font-tty4 console-font-tty5 console-font-tty6 console-font-tty2
console-font-tty3 file-system-/dev/pts syslogd)
Stopped: (ssh-daemon)

Obviously:
deco status networking
No service at all providing networking.

>> I totally understand if you do not want to take up time trying to
>> solve newbie errors. However, my hope is that these problems provide
>> useful information for guix development.
>
> It’s definitely useful!
>
> Thanks,
> Ludo’.


Adam Pribyl

Re: Advice needed on gcc error

[Ludovic Courtès]

Adam Pribyl <pribyl@lowlevel.cz> skribis:

> This is exactly the same thing I am triing to achieve. But the lsh-service
> (ssh-daemon) has a dependency on the networking service, which I am not
> able to provide - this is the reason why I did add also a
> dhcp-client-service, but it seems to not work, as there is no network even
> after reconfigure and reboot.
>
> deco status dmd
> Started: (nscd file-system-/dev/shm dmd host-name term-tty1 loopback
> guix-daemon console-font-tty1 root-file-system user-unmount term-tty4
> term-tty5 udev term-tty6 term-tty2 term-tty3 user-processes
> console-font-tty4 console-font-tty5 console-font-tty6 console-font-tty2
> console-font-tty3 file-system-/dev/pts syslogd)
> Stopped: (ssh-daemon)
>
> Obviously:
> deco status networking
> No service at all providing networking.

Could you post your configuration?

I have something like this:

--8<---------------cut here---------------start------------->8---
  (services (cons* (slim-service)

                   (avahi-service)
                   (dbus-service (list avahi))

                   ;; [...]

                   (lsh-service #:root-login? #t)
                   (dhcp-client-service)

                   %base-services))
--8<---------------cut here---------------end--------------->8---

and ‘deco status networking’ shows the actual service.

Thanks,
Ludo’.

Re: Advice needed on gcc error

[Adam Pribyl]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1191 bytes --]

On Sat, 22 Nov 2014, Ludovic Courtès wrote:

> Adam Pribyl <pribyl@lowlevel.cz> skribis:
>
> Could you post your configuration?
>
> I have something like this:
>
> --8<---------------cut here---------------start------------->8---
>  (services (cons* (slim-service)
>
>                   (avahi-service)
>                   (dbus-service (list avahi))
>
>                   ;; [...]
>
>                   (lsh-service #:root-login? #t)
>                   (dhcp-client-service)
>
>                   %base-services))
> --8<---------------cut here---------------end--------------->8---
>
> and ‘deco status networking’ shows the actual service.


Great, this is it! I had
   (services (cons (dhcp-client-service)
                    %base-services))
   (services (cons (lsh-service #:port-number 22 #:root-login? #t)
                    %base-services))

I understand now it was a nonsence. Using cons* and defining both under 
single service section works now.

Just for the lsh - by default it expects a key under /etc/lsh_host_key, 
while this service definition changes it to /etc/ls/host-key.

> Thanks,
> Ludo’.

Thanks a lot

Adam Pribyl

Re: Advice needed on gcc error

[Ludovic Courtès]

Adam Pribyl <pribyl@lowlevel.cz> skribis:

> Great, this is it! I had
>   (services (cons (dhcp-client-service)
>                    %base-services))
>   (services (cons (lsh-service #:port-number 22 #:root-login? #t)
>                    %base-services))

Oh, OK.  Ideally an error would be raised in such a case.

> Just for the lsh - by default it expects a key under
> /etc/lsh_host_key, while this service definition changes it to
> /etc/ls/host-key.

OK.  Perhaps this should be mentioned in the manual?

Ludo’.

Re: Advice needed on gcc error

[Adam Pribyl]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1427 bytes --]

On Sun, 23 Nov 2014, Ludovic Courtès wrote:

> Adam Pribyl <pribyl@lowlevel.cz> skribis:
>
>> Great, this is it! I had
>>   (services (cons (dhcp-client-service)
>>                    %base-services))
>>   (services (cons (lsh-service #:port-number 22 #:root-login? #t)
>>                    %base-services))
>
> Oh, OK.  Ideally an error would be raised in such a case.

Did not noticed any... guix system reconfigure just finished OK.


>> Just for the lsh - by default it expects a key under
>> /etc/lsh_host_key, while this service definition changes it to
>> /etc/ls/host-key.
>
> OK.  Perhaps this should be mentioned in the manual?

/etc/lsh/host-key

Well it is mostly there as there is and option
[#:host-key "/etc/lsh/host-key"]
Just when one tries to start lshd manually it first prints it needs 
the yarrow seed, then host key in proper location etc. Host key location 
is different.

I would suggest improving the
http://www.gnu.org/software/guix/manual/guix.html#Using-the-Configuration-System
example and incorporating most of the options in the configuration example 
as e.g. starting lsh-service without [#:initialize? #f] for the first 
time makes no sense. Also it could be present in the config template in 
the distribution itself.

This would help most of us not very familiar with all the details to do a 
fluent installation.

> Ludo’.

Regards

Adam Pribyl

Re: Advice needed on gcc error

[Ludovic Courtès]

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

Adam Pribyl <pribyl@lowlevel.cz> skribis:

> I would suggest improving the
> http://www.gnu.org/software/guix/manual/guix.html#Using-the-Configuration-System
> example and incorporating most of the options in the configuration
> example as e.g. starting lsh-service without [#:initialize? #f] for
> the first time makes no sense. Also it could be present in the config
> template in the distribution itself.
>
> This would help most of us not very familiar with all the details to
> do a fluent installation.

I was uneasy having #:initialize? default to #t.  That would work, but
I’d rather have people create key handle that explicitly by themselves,
because it’s pretty sensitive, #:initialize? runs ‘lsh-make-seed’ with
--sloppy, which is not so great, and they might want to reuse existing
keys, etc.

To begin with, I’ve clarified the documention, with links to the lsh
manual (patch below.)

Thanks for the suggestion,
Ludo’.


[-- Attachment #2: Type: text/x-patch, Size: 2761 bytes --]

commit aba747bda84d99fc7dc7b5ff40562217d6d304dc (HEAD, refs/heads/master)
Author: Ludovic Courtès <ludo@gnu.org>
Date:   Mon Nov 24 21:15:40 2014 +0100

    doc: Add xrefs to the lsh manual.
    
    Suggested by Adam Pribyl <pribyl@lowlevel.cz>.
    
    * gnu/services/ssh.scm (lsh-service): Update docstring with xrefs to
      the lsh manual.  Fix typos.
    * doc/guix.texi (Networking Services): Synchronize.

	Modified   doc/guix.texi
diff --git a/doc/guix.texi b/doc/guix.texi
index a2f881f..3d49f7d 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -4033,12 +4033,17 @@ When @var{initialize?} is true, automatically create the seed and host key
 upon service activation if they do not exist yet.  This may take long and
 require interaction.
 
+When @var{initialize?} is false, it is up to the user to initialize the
+randomness generator (@pxref{lsh-make-seed,,, lsh, LSH Manual}), and to create
+a key pair with the private key stored in file @var{host-key} (@pxref{lshd
+basics,,, lsh, LSH Manual}).
+
 When @var{interfaces} is empty, lshd listens for connections on all the
 network interfaces; otherwise, @var{interfaces} must be a list of host names
 or addresses.
 
-@var{allow-empty-passwords?} specifies whether to accepts log-ins with empty
-passwords, and @var{root-login?} specifies whether to accepts log-ins as
+@var{allow-empty-passwords?} specifies whether to accept log-ins with empty
+passwords, and @var{root-login?} specifies whether to accept log-ins as
 root.
 
 The other options should be self-descriptive.
	Modified   gnu/services/ssh.scm
diff --git a/gnu/services/ssh.scm b/gnu/services/ssh.scm
index 5fc98e9..2b52c77 100644
--- a/gnu/services/ssh.scm
+++ b/gnu/services/ssh.scm
@@ -91,12 +91,17 @@ When @var{initialize?} is true, automatically create the seed and host key
 upon service activation if they do not exist yet.  This may take long and
 require interaction.
 
+When @var{initialize?} is false, it is up to the user to initialize the
+randomness generator (@pxref{lsh-make-seed,,, lsh, LSH Manual}), and to create
+a key pair with the private key stored in file @var{host-key} (@pxref{lshd
+basics,,, lsh, LSH Manual}).
+
 When @var{interfaces} is empty, lshd listens for connections on all the
 network interfaces; otherwise, @var{interfaces} must be a list of host names
 or addresses.
 
-@var{allow-empty-passwords?} specifies whether to accepts log-ins with empty
-passwords, and @var{root-login?} specifies whether to accepts log-ins as
+@var{allow-empty-passwords?} specifies whether to accept log-ins with empty
+passwords, and @var{root-login?} specifies whether to accept log-ins as
 root.
 
 The other options should be self-descriptive."