On Tue, 2011-07-05 at 17:06 +0100, david M brooke wrote:
> On 4 Jul 2011, at 23:20, Mike Noyes wrote:
> 
> > On Mon, 2011-07-04 at 23:37 +0200, Erich Titl wrote:
> >> Hi David
> >> 
> >> on 04.07.2011 21:06, david M brooke wrote:
> >>> 
> >> ...
> >>> 
> >>> Hi Mike,
> >>> 
> >>> My build host is running Fedora 15 for x86_64. Works fine. Happy to
> >>> share the logfile from a clean build if that is any use, though it
> >>> will be big...
> >>> 
> >>> Would be good to get an understanding of which build OS platforms
> >>> are OK / not OK to extend the list in the Wiki page. What platforms
> >>> do other developers use?
> >>> 
> >> I don't think we should not limit the development platform to known
> >> working ones but try to find the issue itself.
> > 
> > Erich,
> > Agreed.
> 
> I agree too. I wasn't suggesting limiting the development platforms,
> just understanding what people have found to be successful. If we know
> that e.g. Red Hat and SUSE are OK but Ubuntu is not it might provide
> some clues about the problem.

David,
This is a reasonable early troubleshooting step.


> >> The way I understand it,
> >> it appears to be a PATH/LIBPATH  problem on a particular platform. Also
> >> it appears to be reproducible on a VM and KP could try another distro as
> >> a VM to narrow it down. It may be that this issue is just the tip of an
> >> iceberg showing up on a particular library environment.

-- 
Mike Noyes
http://sourceforge.net/users/mhnoyes
https://profiles.google.com/mhnoyes


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to