From: ChIIph <chiiph@gmail.com>
To: gentoo-lisp@lists.gentoo.org
Subject: Re: [gentoo-lisp] Ebuilds for bigloo3.3a_p4 and hop-2.0.0
Date: Thu, 14 Jan 2010 17:15:07 -0300 [thread overview]
Message-ID: <4B4F7B4B.4030905@gmail.com> (raw)
In-Reply-To: <4B4F5A47.6040508@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
On 01/14/10 14:54, Cyprien Nicolas wrote:
> Hello lispers,
>
> I'm attaching to this mail two ebuild for the last releases of Bigloo
> and Hop, I have mainly adapted the existing ebuilds.
>
Hello Cyprien,
Thanks for providing these ebuilds, I'll make sure they are added to the
overlay today.
> Some notes, about the bigloo.ebuild:
>
> I have to had the threads flag, for dependencies, hop[threads] needs
> bigloo[threads], which needs boehm-gc[threads]. That makes the hop
> ebuild with three dependencies on hop, I don't know how to make it
> clearer, or better.
>
There was an issue with a bundled copy of boegm-gc, I hope Mr Serrano
took care of that :), otherwise some patching must be made for security
reasons.
> Then, I had to manually had -fno-omit-frame-pointer to Bigloo's CFLAGS,
> for several reasons:
> First, for compile-bee, part of the code may be compiled with -pg flag
> (for gprof profiling), this option is incompatible with
> -fomit-frame-pointer.
> Next, at runtime, Bigloo uses the CFLAGS he got at compile time when
> calling GCC on the produced C file. so bigloo -p will call gcc -pg (if
> enabled), then raise a gcc error.
>
Yes, I've bumped up to this problem too.
Strictly "ebuild-speaking", the best way to handle this is with the
eclass flag-o-matic, removing -fomit-frame-pointer. Either way, you are
right, that flag must be disabled.
>
> This ebuild has been ran on both x86 hardened and x86_64 hardened
> systems, without any issue except the -pg thing I have bypassed.
>
Great, thanks for the testing.
Regards,
Tomas
>
>
> Any comment are welcome
>
>
> Regards,
>
> ,Cyprien
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-14 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 17:54 [gentoo-lisp] Ebuilds for bigloo3.3a_p4 and hop-2.0.0 Cyprien Nicolas
2010-01-14 20:15 ` ChIIph [this message]
2010-01-29 12:51 ` Cyprien Nicolas
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=4B4F7B4B.4030905@gmail.com \
--to=chiiph@gmail.com \
--cc=gentoo-lisp@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox