From: "Gábor Boskovits" <boskovits@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gcc-ddc
Date: Sat, 2 Dec 2017 15:53:25 +0100 [thread overview]
Message-ID: <CAE4v=pjiDOverLCR=r5fV_uY-0E7=aXoSXMgPdD+=8EBfxmjYg@mail.gmail.com> (raw)
In-Reply-To: <87mv31dw43.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
Ok, I will do that.
I can eliminate differences in the wrappers easily, then I will look into
the libtool patch.
It seems, that the la files are causing the checksum difference in cc1 and
cc1plus, because if I remove libraries from the checksum, then they agree.
I also checked the same things when I compile with clang. The differences
are the same, so we can do this. The rest is just "cosmetics".
2017-12-02 15:48 GMT+01:00 Jan Nieuwenhuizen <janneke@gnu.org>:
> Gábor Boskovits writes:
>
> > Aside from these libtool files we can now say, that this ddc project
> succeeded.
>
> Wait... The libtool's .la files are now the only files that show any
> difference, even when gcc is compiled into it's own prefix? That's
> amazing!!!
>
> > I've contacted the libtool developers if we can extend the wrapper
> approach to the .la files.
>
> Great!
>
> > It seems, that in some older version of libtool those were just sourced
> as shell script, but
> > I don't know if now they do something more fancy with it or not...
> > Anyways, if it's just shell script, then the environment variable
> approach can also work out there.
> > The only problem seems, that I should do the substitution before
> checksumming the compiler.
> > I think I can inject something into the makefile, or use a patched
> vesion of libtool.
> >
> > A patched libtool could be a better option, so other ddc projects can
> use it.
>
> Indeed.
>
> > I guess I can do something like add an environment variable
> GUIX_INSTALL_DIRECTORY, or something like that...
>
> What's different about GUIX_INSTALL_DIRECTORY than the usual: PREFIX?
>
> > Any maybe name this version libtool-for-ddc.
> > It should be noted in the package documentation, that this package is
> not recommended for general use.
>
> Are you proposing to patch libtool? If so, even if patching it for
> [gcc-]dcc only would be a great hack for now. Please go forward with
> that idea at least until libtool devs help us with a full solution.
>
> janneke
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
> Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
>
[-- Attachment #2: Type: text/html, Size: 3090 bytes --]
next prev parent reply other threads:[~2017-12-02 14:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAE4v=phLKD_nOD2CeBB26H2wDcJuwQsg1Y09BprjMg_YQq2ahw@mail.gmail.com>
2017-11-20 18:24 ` gcc-ddc Jan Nieuwenhuizen
2017-11-20 22:14 ` gcc-ddc Ricardo Wurmus
2017-11-20 23:16 ` gcc-ddc Gábor Boskovits
2017-11-21 16:36 ` gcc-ddc Gábor Boskovits
2017-11-21 16:48 ` gcc-ddc Gábor Boskovits
2017-11-21 22:01 ` gcc-ddc Jan Nieuwenhuizen
2017-11-22 14:42 ` gcc-ddc Gábor Boskovits
2017-11-23 4:11 ` gcc-ddc Jan Nieuwenhuizen
2017-11-23 7:14 ` gcc-ddc Ricardo Wurmus
2017-11-23 11:23 ` gcc-ddc Gábor Boskovits
2017-11-29 9:43 ` gcc-ddc Gábor Boskovits
2017-11-29 12:26 ` gcc-ddc Gábor Boskovits
2017-11-29 15:57 ` gcc-ddc Jan Nieuwenhuizen
2017-11-30 14:32 ` gcc-ddc Gábor Boskovits
2017-12-01 15:44 ` gcc-ddc Gábor Boskovits
2017-12-02 14:48 ` gcc-ddc Jan Nieuwenhuizen
2017-12-02 14:53 ` Gábor Boskovits [this message]
2017-12-02 22:44 ` gcc-ddc Ricardo Wurmus
2018-01-29 8:46 ` gcc-ddc Gábor Boskovits
2018-01-29 14:14 ` gcc-ddc Ludovic Courtès
2018-01-29 14:25 ` gcc-ddc Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pjiDOverLCR=r5fV_uY-0E7=aXoSXMgPdD+=8EBfxmjYg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=janneke@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).