--- Nupur <[EMAIL PROTECTED]> wrote:
> I think, I should have told this to you before that
> I have upgraded
> the bash on my computer as well. I have upgraded it
> to 3.0
> So, this might be the case that the newer version of
> bash does not
> support the older method, i.e., ' ...'
> No issues,
> I've no more idea what it can be. According to bash
> (and other shells I looked at), `command` and
> $(command) are equivalent for command substitution.
> The second form is the newer. So I can only recommand
> you to always use $(...) instead of `...` in all your
> commands, it should be strict
--- Nupur <[EMAIL PROTECTED]> wrote:
> I apologize for replying so late. G. Moko, after
> trying with the first
> command you asked me to; i.e.,
> ./configure --prefix=$(pkg-config --variable=prefix
> ORBit-2.0)
> --libexecdir=$(pkg-config --variable=prefix
> ORBit-2.0)/sbin
> --sysconfdir=/etc/gn
On 11/17/05, go moko <[EMAIL PROTECTED]> wrote:
> --- Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> > Nupur wrote these words on 11/17/05 09:15 CST:
> >
> > > Then, I ran the checked PKG_CONFIG_PATH by echo
> > $PKG_CONFIG_PATH and
> > > it returned:
> > > /usr/lib/pkgconfig/
> >
> > And that is wh
go moko wrote these words on 11/17/05 09:38 CST:
> I don't remember Nupur mentionned /opt.
> Gnome-pre-install-config suggest to install in /usr or
> in /opt/gnome, and I guess Nupur choose the first
> solution.
Ahh, I see that now. My bad.
--
Randy
rmlscsi: [GNU ld version 2.15.94.0.2 2004122
--- Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Nupur wrote these words on 11/17/05 09:15 CST:
>
> > Then, I ran the checked PKG_CONFIG_PATH by echo
> $PKG_CONFIG_PATH and
> > it returned:
> > /usr/lib/pkgconfig/
>
> And that is why your initial installation to /opt
> didn't work. You
> failed t
Nupur wrote these words on 11/17/05 09:15 CST:
> Then, I ran the checked PKG_CONFIG_PATH by echo $PKG_CONFIG_PATH and
> it returned:
> /usr/lib/pkgconfig/
And that is why your initial installation to /opt didn't work. You
failed to add the additional path into your environment so that the
PKG_CON
On 11/17/05, go moko <[EMAIL PROTECTED]> wrote:
> --- Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> > go moko wrote these words on 11/17/05 07:06 CST:
> > > Another method
> > > is to use a variable GNOME_PATH and put everywhere
> > > "--prefix=$GNOME_PATH" (as for KDE, if my memory
> > is
> > > go
--- Randy McMurchy <[EMAIL PROTECTED]> wrote:
> go moko wrote these words on 11/17/05 07:06 CST:
> > Another method
> > is to use a variable GNOME_PATH and put everywhere
> > "--prefix=$GNOME_PATH" (as for KDE, if my memory
> is
> > good).
>
> Well, the book already specifies to use
> $GNOME_PREF
Nupur wrote these words on 11/17/05 07:14 CST:
> I did that as well. I tried typing the command (without any quotes)
> "pkg-config --variable=prefix ORBit-2.0"
> and got the result as /usr. So, I could deduce that pkg-config is
> also working fine. After getting the result from this command, I
> u
go moko wrote these words on 11/17/05 07:06 CST:
> Another method
> is to use a variable GNOME_PATH and put everywhere
> "--prefix=$GNOME_PATH" (as for KDE, if my memory is
> good).
Well, the book already specifies to use $GNOME_PREFIX for the Orbit
installation, might as well suggest to use that
>
> I think the problem is in pkg-config, not in ORBit.
> PKG_CONFIG_PATH must not be initialised properly in
> the environment. You can test that by just launching
> the command "pkg-config --variable=prefix ORBit-2.0"
> in a shell and see the result.
> However, the use of this command to find the
--- Nupur <[EMAIL PROTECTED]> wrote:
> On 11/17/05, Randy McMurchy
> <[EMAIL PROTECTED]> wrote:
> > Nupur wrote these words on 11/17/05 06:35 CST:
> >
> > > I used the backticks. I am using the command
> same as mentioned in the
> > > book. But now, I have compiled using /usr
> instead and it comp
On 11/17/05, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Nupur wrote these words on 11/17/05 06:35 CST:
>
> > I used the backticks. I am using the command same as mentioned in the
> > book. But now, I have compiled using /usr instead and it compiled
> > fine.
>
> Then, the only thing that can mean
Nupur wrote these words on 11/17/05 06:35 CST:
> I used the backticks. I am using the command same as mentioned in the
> book. But now, I have compiled using /usr instead and it compiled
> fine.
Then, the only thing that can mean is you didn't install the Orbit
package.
BTW, what version of LFS/
On 11/17/05, Andrew Benton <[EMAIL PROTECTED]> wrote:
> Nupur wrote:
> > Dear All,
> >
> > I am getting an error while configuring libbonobo-2.8.1 for GNOME.
> >
> > The error is listed below:
> >
> > configure: error: expected an absolute dir
Nupur wrote:
Dear All,
I am getting an error while configuring libbonobo-2.8.1 for GNOME.
The error is listed below:
configure: error: expected an absolute directory name for --prefix:
pkg-config --variable=prefix ORBit-2.0
It looks like you didn't use backticks `` when you configur
On 11/17/05, go moko <[EMAIL PROTECTED]> wrote:
> --- Nupur <[EMAIL PROTECTED]> wrote:
>
> > Dear All,
> >
> > I am getting an error while configuring
> > libbonobo-2.8.1 for GNOME.
> >
> > The error is listed below:
> >
> > conf
--- Nupur <[EMAIL PROTECTED]> wrote:
> Dear All,
>
> I am getting an error while configuring
> libbonobo-2.8.1 for GNOME.
>
> The error is listed below:
>
> configure: error: expected an absolute directory
> name for --prefix:
> pkg-config --variable=pr
Dear All,
I am getting an error while configuring libbonobo-2.8.1 for GNOME.
The error is listed below:
configure: error: expected an absolute directory name for --prefix:
pkg-config --variable=prefix ORBit-2.0
I have installed ORBit as well as pkg-config successfully.
One thing also, I would
20 matches
Mail list logo
