From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-devhelp@lists.gentoo.org
Subject: [gentoo-devhelp] Re: package.env files error: unexpected EOF while looking for matching `}'
Date: Sun, 03 Jun 2012 18:58:49 +0300 [thread overview]
Message-ID: <jqg1ks$11l$1@dough.gmane.org> (raw)
In-Reply-To: <4FCB7CBA.708@orlitzky.com>
On 03/06/12 18:03, Michael Orlitzky wrote:
> On 06/03/2012 08:55 AM, Nikos Chantziaras wrote:
>> package.env really hates me. It seems I can do nothing useful with it.
>> I'm trying to remove a compiler flag:
>>
>> CFLAGS=${CFLAGS//-flto/}
>> CXXFLAGS=${CXXFLAGS//-flto/}
>> LDFLAGS=${LDFLAGS//-flto/}
>>
>> However:
>>
>> "/etc/portage/env/no-lto.conf", line 2: unexpected EOF while looking for
>> matching `}'
>> "/etc/portage/env/no-lto.conf", line 3: unexpected EOF while looking for
>> matching `}'
>> "/etc/portage/env/no-lto.conf", line 4: unexpected EOF while looking for
>> matching `}'
>> /"/etc/portage/env/no-lto.conf", line 2: unexpected EOF while looking
>> for matching `}'
>> "/etc/portage/env/no-lto.conf", line 3: unexpected EOF while looking for
>> matching `}'
>> "/etc/portage/env/no-lto.conf", line 4: unexpected EOF while looking for
>> matching `}'
>>
>> The string replacement syntax looks correct to me. What am I doing wrong?
>>
>>
>
> I think I ran into this too. Basically, you can wind up with two
> different kinds of parsers depending on where you stick your file:
>
> http://bugs.gentoo.org/show_bug.cgi?id=388781
>
> Looks like you're getting the make.conf-like parser instead of the
> bashrc one.
Simple assignment is the *only* thing that parser can do?
next prev parent reply other threads:[~2012-06-03 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 12:55 [gentoo-devhelp] package.env files error: unexpected EOF while looking for matching `}' Nikos Chantziaras
2012-06-03 15:03 ` Michael Orlitzky
2012-06-03 15:58 ` Nikos Chantziaras [this message]
2012-06-03 18:25 ` [gentoo-devhelp] " Michael Orlitzky
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='jqg1ks$11l$1@dough.gmane.org' \
--to=realnc@gmail.com \
--cc=gentoo-devhelp@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