From: Alex Vong <alexvong1995@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] daemon: Fix '--version'.
Date: Tue, 30 Aug 2016 12:29:22 +0800 [thread overview]
Message-ID: <8760qi282l.fsf@gmail.com> (raw)
In-Reply-To: <87vayjy2nq.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 29 Aug 2016 18:12:57 +0200")
Hello,
ludo@gnu.org (Ludovic Courtès) writes:
> Hi!
>
> Alex Vong <alexvong1995@gmail.com> skribis:
>
>> This one and the next patch fix '--version' of guix-daemon and
>> guix-register. Currently, they are not working, which is the reason why
>> help2man gives error when building from source.
>
> How are they not working exactly? :-)
>
> It definitely works for me:
>
> $ ./guix-daemon --version
> guix-daemon (GNU Guix) 0.11.0
> $ ./guix-register --version
> guix-register (GNU Guix) 0.11.0
>
I get this output instead:
$ LC_ALL=C ./guix-daemon --version
./guix-daemon: unrecognized option '--version'
Try `guix-daemon --help' or `guix-daemon --usage' for more information.
This is werid, but I think it is because I build guix with lto.
Here is how I build guix:
$ ./bootstrap && ./configure CFLAGS='-O2 -flto' CXXFLAGS='-O2 -flto' LDFLAGS='-O2 -flto' && make -j`nproc` AR=gcc-ar NM=gcc-nm RANLIB=gcc-ranlib
So, perhaps this is a gcc bug! (not guix's one, we can forget about the
patch)
Could you reproduce it?
> Ludo’.
Thanks,
Alex
next prev parent reply other threads:[~2016-08-30 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 1:34 [PATCH 1/2] daemon: Fix '--version' Alex Vong
2016-08-29 1:31 ` (ping!) " Alex Vong
2016-08-29 16:12 ` Ludovic Courtès
2016-08-30 4:29 ` Alex Vong [this message]
2016-08-31 21:13 ` Ludovic Courtès
2016-09-01 6:23 ` Alex Vong
2016-09-01 12:15 ` Ludovic Courtès
2016-09-02 1:00 ` Alex Vong
2016-09-02 12:41 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760qi282l.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.