On Mon, May 5, 2008 at 5:59 PM, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> On Mon, 05 May 2008 22:03:27 +0200, Lucas C. Villa Real <[EMAIL PROTECTED]>
> wrote:
>
> > On Mon, May 5, 2008 at 4:58 PM, Hisham <[EMAIL PROTECTED]> wrote:
> >> On Mon, May 5, 2008 at 10:48 AM, <[EMAIL PROTECTED]> wrote:
> >> > Author: mohjive
> >> > Date: 2008-05-05 06:48:01 -0700 (Mon, 05 May 2008)
> >> > New Revision: 3296
> >> >
> >> > Modified:
> >> > trunk/ChrootCompile/bin/ChrootCompile
> >> > Log:
> >> > We have to process each environment line by itself
> >>
> >> Why is this so? This breaks env files with multi-line entries (e.g.
> >> the Lua Environment file for Lua).
>
> Do the Lua recipe have to have multiple lines, or can one put the
> export statement on one line?
Almost anything in bash can be compressed into one-liner format, but
Environment files never had this restriction and I don't think they
should have.
> > Processing the environment files at once, as we were doing, was
> > working fine for me here. It's easy to reproduce and test that in the
> > shell.
> >
> It did not work for me. CPLUS_INCLUDE_PATH and C_INCLUDE_PATH were not
> updated, even though the gcc Environment file tried to set them with
> the statements below:
>
> export
> CPLUS_INCLUDE_PATH="${goboHeaders}/c++/4.3.0:${goboHeaders}${CPLUS_INCLUDE_PATH:+:$CPLUS_INCLUDE_PATH}"
> export C_INCLUDE_PATH="${goboHeaders}${C_INCLUDE_PATH:+:$C_INCLUDE_PATH}"
It may be some other problem. It is certainly possible to eval
multi-line sequences:
~]bash
~]unset FOO
~]unset BAR
~]cat test.sh
export FOO="foo"
export BAR="bar"
~]eval `cat test.sh`
~]echo $FOO
foo
~]echo $BAR
bar
-- Hisham
_______________________________________________
gobolinux-devel mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
