all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] daemon: Fix '--version'.
Date: Fri, 02 Sep 2016 14:41:37 +0200	[thread overview]
Message-ID: <878tvamq2m.fsf@gnu.org> (raw)
In-Reply-To: <87d1knazeh.fsf@gmail.com> (Alex Vong's message of "Fri, 02 Sep 2016 09:00:54 +0800")

Alex Vong <alexvong1995@gmail.com> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Alex Vong <alexvong1995@gmail.com> skribis:
>>
> [...]
>>>
>>> I think you have isolated the problem! This test case does not work for
>>> me.
>>>
>>>
>>> I get the following output after building with
>>> (g++ -O2 -flto version.cxx):
>>
>> What if you compile with ‘gcc’ (and rename to foo.c) instead of ‘g++’?
>>
>> It might be a symbol visibility problem, or name mangling issue.
>>
>> Ludo’.
>
> Hmm, I try to build with 'gcc -O2 -flto version.c' and './a.out
> --version' still fails with 'unrecognized option'. I check the symbols
> using 'nm' and they are not mangled. How should I check for the sign of
> a symbol visibility problems? 

‘nm’ shows a capital T for exported symbols, and a lowercase t for
hidden/private symbols.

Maybe you should report a bug against your distro’s package and see what
they think?

Ludo’.

      reply	other threads:[~2016-09-02 12:41 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
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 [this message]

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=878tvamq2m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alexvong1995@gmail.com \
    --cc=guix-devel@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.