The_UnNamed_One

View: New views
5 Messages — Rating Filter:   Alert me  

The_UnNamed_One

by Erich Titl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Folks

I decided to give it a try and build a buildenv. Unfortunately I did not
get very far

source/package: linux
------------------------
downloading: buildtool.cfg from server cvs-sourceforge type file
download failed: file ../apps/linux/buildtool.cfg does not exist

you might find useful information in log/buildtoollog

......

buildtool::Common::InstalledFile::searchInstalled4Pkg:starting
buildtool::Common::InstalledFile::searchInstalled4Pkg:entry buildenv not
in source list
buildtool::Make::Source::_makeCompleteList:buildenv added to complete
list list
buildtool::Download::setDlroot:setting dlroot to :
/data/leaf/bering-uclibc/devel/latest/2.6/The_UnNamed_One/buildtool/source/linux
buildtool::Download::download:file key: buildtool.cfg
checking link /lib/ld-uClibc.so

cheers

Erich

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

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

Re: The_UnNamed_One

by Martin Hejl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Erich,

> I decided to give it a try and build a buildenv. Unfortunately I did not
> get very far
>
> source/package: linux
> ------------------------
> downloading: buildtool.cfg from server cvs-sourceforge type file
> download failed: file ../apps/linux/buildtool.cfg does not exist

The following worked for me a few minutes ago (which is the approach I
outlined in my email to leaf-devel on March 1st 2008):

export CVS_RSH=ssh
cvs -z3 -d:ext:hejl@...:/cvsroot/leaf \
  co src/The_UnNamed_One

    (obviously, you'll have to replace "hejl" with your SF username)

cd src/The_UnNamed_One/buildtool/

vi make/MasterInclude.mk

   To make sure HOSTCC points to a gcc 3.x - gcc 4.x might not work, I
   don't know if the patches kp committed to the Bering uClibc branch
   made it into "The_UnNamed_One")

./buildtool.pl build buildenv

Since it was "work in progress" when I committed it, I went for
expecting a local checkout of the apps directory (that's more convenient
during development anyway).

I hope that helps,

Martin


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

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

Re: The_UnNamed_One

by Martin Hejl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi again,

ok, forget what I just wrote - the instructions below are no longer
accurate, since kp just changed the config in CVS

Martin

Martin Hejl schrieb:

> Hi Erich,
>
>> I decided to give it a try and build a buildenv. Unfortunately I did not
>> get very far
>>
>> source/package: linux
>> ------------------------
>> downloading: buildtool.cfg from server cvs-sourceforge type file
>> download failed: file ../apps/linux/buildtool.cfg does not exist
>
> The following worked for me a few minutes ago (which is the approach I
> outlined in my email to leaf-devel on March 1st 2008):
>
> export CVS_RSH=ssh
> cvs -z3 -d:ext:hejl@...:/cvsroot/leaf \
>   co src/The_UnNamed_One
>
>     (obviously, you'll have to replace "hejl" with your SF username)
>
> cd src/The_UnNamed_One/buildtool/
>
> vi make/MasterInclude.mk
>
>    To make sure HOSTCC points to a gcc 3.x - gcc 4.x might not work, I
>    don't know if the patches kp committed to the Bering uClibc branch
>    made it into "The_UnNamed_One")
>
> ./buildtool.pl build buildenv
>
> Since it was "work in progress" when I committed it, I went for
> expecting a local checkout of the apps directory (that's more convenient
> during development anyway).
>
> I hope that helps,
>
> Martin
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>
> _______________________________________________
> leaf-devel mailing list
> leaf-devel@...
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
>
>

--
You think that's tough?  Try herding cats!

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

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

Re: The_UnNamed_One

by KP Kirchdoerfer-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Am Freitag, 7. August 2009 12:14:04 schrieb Martin Hejl:

> Hi Erich,
>
> > I decided to give it a try and build a buildenv. Unfortunately I did not
> > get very far
> >
> > source/package: linux
> > ------------------------
> > downloading: buildtool.cfg from server cvs-sourceforge type file
> > download failed: file ../apps/linux/buildtool.cfg does not exist
>
> The following worked for me a few minutes ago (which is the approach I
> outlined in my email to leaf-devel on March 1st 2008):
>
> export CVS_RSH=ssh
> cvs -z3 -d:ext:hejl@...:/cvsroot/leaf \
>   co src/The_UnNamed_One
>
>     (obviously, you'll have to replace "hejl" with your SF username)
>
> cd src/The_UnNamed_One/buildtool/
>
> vi make/MasterInclude.mk
>
>    To make sure HOSTCC points to a gcc 3.x - gcc 4.x might not work, I
>    don't know if the patches kp committed to the Bering uClibc branch
>    made it into "The_UnNamed_One")
>
> ./buildtool.pl build buildenv
>
> Since it was "work in progress" when I committed it, I went for
> expecting a local checkout of the apps directory (that's more convenient
> during development anyway).
>
> I hope that helps,
>
> Martin

Hi;

just committed a few minutes ago the change for compilation with a recent gcc
(obstack.h.patch) and a sources.cfg which points to sourceforge cvs by
default.

Tested with gcc4.2.4 and buildenv built without errors.

kp

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

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

Parent Message unknown Re: The_UnNamed_One

by Martin Hejl :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Erich,

> Somehow this HOSTCC stuff is weird, in the process of building buildenv
> a gcc 3.3.3 is downloaded, despite all definitions im MasterInclude.mk.
I'm not sure what's so weird about it - it works the exact same way as
the Bering uClibc branch (unless things have changed since early 2008).

Buildenv builds a gcc that is linked against uClibc - in order to do
that, it needs a host CC that will be able to compile the gcc we provide
(which happens to be 3.3.3 at the moment, since newer versions caused
all kinds of problems). gcc 4.x is not able to compile a vanilla gcc
3.3, so in the past we needed a gcc 3.x on the host in order to build
the toolchain.

With the patches kp committed on friday, you should be able to use a
newer gcc as the "host cc" as well (but I can't say for sure, since I
haven't tried it).

> Now which one is supposed to be used?
Both. HOSTCC (which must be installed on your system before you do
anything with buildtool - again, the same approach as with Bering
uClibc) for building the first part of the toolchain, and gcc 3.3.3
which is part of the toolchain.

I hope that helps

Martin



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

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