From: Peter Volkov <pva@gentoo.org>
To: Nikos Chantziaras <realnc@arcor.de>
Cc: gentoo-devhelp@lists.gentoo.org
Subject: Re: [gentoo-devhelp] Re: How do I make scons use correct CFLAGS/CXXFLAGS/LDFLAGS?
Date: Tue, 17 May 2011 22:58:59 +0400 [thread overview]
Message-ID: <1305658739.19924.2.camel@tablet> (raw)
In-Reply-To: <iqu4t9$vtq$1@dough.gmane.org>
В Втр, 17/05/2011 в 18:40 +0300, Nikos Chantziaras пишет:
> On 05/17/2011 11:57 AM, Peter Volkov wrote:
> > В Втр, 17/05/2011 в 10:18 +0300, Nikos Chantziaras пишет:
> >> On 05/17/2011 09:45 AM, Peter Volkov wrote:
> >>> В Втр, 17/05/2011 в 08:23 +0300, Nikos Chantziaras пишет:
> >>>> scons: *** Path for option install_path does not exist:
> >>>> /var/tmp/portage/dev-util/gpuocelot-9999/image
> >>>
> >>> Please, post full ebuild.
> >
> >> src_compile() {
> >> tc-export CC CXX
> >> escons install_path="${D}"/usr test_level=none || die
> >
> > You don't need install_path here, only in src_install().
>
> Removing it brings us back to the original problem:
>
> g++ -o .release_build/OcelotConfig -L/usr/lib64/llvm -lpthread -lffi
> -ldl -lm .release_build/ocelot/tools/OcelotConfig.o -L/usr/lib
> -L/usr/lib64/llvm -L. -locelot
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/../../../../x86_64-pc-linux-gnu/bin/ld:
> cannot find -locelot
> collect2: ld returned 1 exit status
Looks like this is bug in build system not in ebuild. Try to build
manually and if that fails then either fix it or report upstream.
--
Peter.
next prev parent reply other threads:[~2011-05-17 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 3:48 [gentoo-devhelp] How do I make scons use correct CFLAGS/CXXFLAGS/LDFLAGS? Nikos Chantziaras
2011-05-17 4:49 ` [gentoo-devhelp] " Nikos Chantziaras
2011-05-17 5:14 ` Nathan Phillip Brink
2011-05-17 5:23 ` Nikos Chantziaras
2011-05-17 6:45 ` Peter Volkov
2011-05-17 7:18 ` Nikos Chantziaras
2011-05-17 8:57 ` Peter Volkov
2011-05-17 15:40 ` Nikos Chantziaras
2011-05-17 18:58 ` Peter Volkov [this message]
2011-05-17 19:12 ` Nikos Chantziaras
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=1305658739.19924.2.camel@tablet \
--to=pva@gentoo.org \
--cc=gentoo-devhelp@lists.gentoo.org \
--cc=realnc@arcor.de \
/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