From: Al <oss.elmar@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gawk and filefuncs
Date: Sat, 4 Sep 2010 12:51:29 +0200 [thread overview]
Message-ID: <AANLkTinRxZ0kn1v3mnBomNC8AJJuAmRWQaQU==nWWKs5@mail.gmail.com> (raw)
In-Reply-To: <20100904105851.6406a06d@scooter.muppet.show>
>> You say it is mandatory on a Gentoo system, because there are awk
>> scripts that rely on. Do this functions break because of the missing
>> kernel? What would be the workaround?
>
> How are you building it? It needs special commands because it needs to
> become a shared object, not an executable.
>
Here is how I am building it and the whole context:
http://en.gentoo-wiki.com/wiki/Prefix/Cygwin#gawk-3.1.7:_.5Bfilefuncs.so.0.0.1.5D_Error_1
emerge --oneshot gawk
> Note that building that file is by no means necessary for a working gawk.
>
> And, even if you built it, it wouldn't do anything unless you specifically
> used the extension() gawk command to reference the object file and import
> the extra definitions (see the link I posted in the first email for all
> the gory details. Also the Makefile that comes with Gentoo's own
> filefuncs.c may help).
I did understand, that it is an extension, which provides additional
commands for awk scripts and that the gentoo system makes use of them
especially of it's own additions.
Options:
1.) It would compile on Cygwin. I just made a mistake.
2.) It depends on the missing kernel. I have to rewrite Gentoos
filefuncs.c to work without a linux kernel.
3.) I can go with the original extension. Portage does not really
depend on Gentoos additions.
4.) I have to adapt all awk scripts that make use of it.
Al
prev parent reply other threads:[~2010-09-04 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 20:31 [gentoo-user] gawk and filefuncs Al
2010-09-03 21:04 ` Etaoin Shrdlu
2010-09-03 22:25 ` Al
2010-09-03 22:26 ` Al
2010-09-04 9:58 ` Etaoin Shrdlu
2010-09-04 10:51 ` Al [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='AANLkTinRxZ0kn1v3mnBomNC8AJJuAmRWQaQU==nWWKs5@mail.gmail.com' \
--to=oss.elmar@googlemail.com \
--cc=gentoo-user@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