[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Re: Yet another installation problem
From: |
Elaine Garbarine |
Subject: |
Re: [Discuss-gnuradio] Re: Yet another installation problem |
Date: |
Wed, 22 Feb 2006 10:09:53 -0500 |
User-agent: |
Microsoft-Entourage/11.2.1.051004 |
Eric,
I'm building on Red Hat 9 and I think this is an older version of the
gr-usrp module than the one that is in CVS. I will checkout and update my
packages and report back.
Also, I configured all packages with the same prefix and set my
PKG_CONFIG_PATH appropriately and I didn't have this problem with any of the
other modules.
I'll do a CVS checkout just to be sure and attempt a rebuild and let you
know what the result was.
-Elaine
On 2/22/06 1:55 AM, "Eric Blossom" <address@hidden> wrote:
> On Tue, Feb 21, 2006 at 01:55:31PM -0500, Elaine Garbarine wrote:
>> I know this is an old message to resurrect but I wanted to let you guys know
>> I found out what the problem was incase anyone comes across this problem in
>> the future.
>>
>> I took a look at Makefile.am in gr-usrp/src and it looks for gnuradio.i by
>> checking the following:
>>
>> NON_LOCAL_IFILES=
>> $(GNURADIO_CORE_INCLUDEDIR)/swig/gnuradio.i
>>
>> For one reason or another none of the environmental variables I had set were
>> pointing the makefile in the correct direction. To fix this I included an
>> additional environmental variable set for the path where /swig/gnuradio.i
>> could be found as follows:
>>
>> Export GNURADIO_CORE_INCLUDEDIR=/usr/gr/include/gnuradio
>>
>> This fixed my issue and gr-usrp completed make and make install without any
>> other problems.
>>
>> Regards,
>> Elaine
>
> Elaine,
>
> This shouldn't be required. I wouldn't expect you to have to
> set any environment variables except possibly PKG_CONFIG_PATH. Just
> use "./configure --prefix=foo" if you're installing in a non-standard
> place.
>
> Are all of gnuradio-core and gr-* configured with the same --prefix ?
>
> Can you send me a transcript (off list) of all the commands (and
> output to stdout and stderr) to reproduce the problem, starting from a
> fresh CVS checkout?
>
> Also, which os and version are you building on?
>
> Please include the output of:
>
> $ env
>
> Thanks,
> Eric