[Buildroot] using linux 2.4 headers

[Buildroot] using linux 2.4 headers

[Tobias McNulty]

I just downloaded the latest version of buildroot and managed to build a
very small file system that includes python and sqlite (exactly what I'm
looking for!) in no time at all.  Very impressed, thanks for all your
hard work everyone!

Now, pardon my ignorance, but is there a way to make buildroot use linux
2.4 headers instead of the default 2.6?  I only have 2 options when I go
to select the kernel headers, and they're both fairly recent iterations
of the 2.6 kernel.

I see that ?Clibc supports 2.4 or greater, but I don't see any mention
of 2.4 in the buildroot docs.

The file system I'm trying to build is for a TS-7400 (arm) and the 2.6
kernel support doesn't seem that great unfortunately.

Thanks
Tobias
-- 
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com

[Buildroot] using linux 2.4 headers

[Peter Korsgaard]

>>>>> "Tobias" == Tobias McNulty <tobias@caktusgroup.com> writes:

Hi,

 Tobias> I just downloaded the latest version of buildroot and managed
 Tobias> to build a very small file system that includes python and
 Tobias> sqlite (exactly what I'm looking for!) in no time at all.
 Tobias> Very impressed, thanks for all your hard work everyone!

Thanks.

 Tobias> Now, pardon my ignorance, but is there a way to make
 Tobias> buildroot use linux 2.4 headers instead of the default 2.6?
 Tobias> I only have 2 options when I go to select the kernel headers,
 Tobias> and they're both fairly recent iterations of the 2.6 kernel.

The 2009.02 release had support for 2.4.41 if you go to build
options->Show packages that are deprecated or obsolete, but we have
removed it from subversion after the release.

Notice though that there aren't many people using the 2.4 support, so
something might not work ..

-- 
Bye, Peter Korsgaard

[Buildroot] using linux 2.4 headers AND python

[Tobias McNulty]

Peter Korsgaard wrote:
> The 2009.02 release had support for 2.4.41 if you go to build
> options->Show packages that are deprecated or obsolete, but we have
> removed it from subversion after the release.
> 
> Notice though that there aren't many people using the 2.4 support, so
> something might not work ..

Thanks that seemed to work.  I had to add some typedefs for __u32 and
__u8 to watchdog.h but otherwise it built fine.  There is probably a
smarter fix.

Upon further investigation Python doesn't seem to be complete though:

$ python -v
Could not find platform independent libraries <prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
# installing zipimport hook
import zipimport # builtin
# installed zipimport hook
'import site' failed; traceback:
ImportError: No module named site
Python 2.4.5 (#1, Mar 24 2009, 23:15:27)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named os
>>>

and, sure enough, I don't see os.py anywhere on the filesystem.  I have
not looked at the python build output yet but I'll do that tomorrow when
I'm more awake.

(It was also this way before the rebuild, the switch to 2.4 did not
introduce the problem.)

Toby
-- 
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com

[Buildroot] using linux 2.4 headers AND python

[Tobias McNulty]

Tobias McNulty wrote:
> Upon further investigation Python doesn't seem to be complete though:
> 
> $ python -v
> Could not find platform independent libraries <prefix>
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> # installing zipimport hook
> import zipimport # builtin
> # installed zipimport hook
> 'import site' failed; traceback:
> ImportError: No module named site
> Python 2.4.5 (#1, Mar 24 2009, 23:15:27)
> [GCC 4.3.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import os
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> ImportError: No module named os
> 
> and, sure enough, I don't see os.py anywhere on the filesystem.  I have
> not looked at the python build output yet but I'll do that tomorrow when
> I'm more awake.

Sure enough, the installer is installing all the .py files and then
removing them again.  It appears the line at fault is the last one in
the following section of python.mk

ifneq ($(BR2_PACKAGE_PYTHON_DEV),y)
        rm -rf $(TARGET_DIR)/usr/include/python$(PYTHON_VERSION_MAJOR)
        rm -rf
$(TARGET_DIR)/usr/lib/python$(PYTHON_VERSION_MAJOR)/config
        find $(TARGET_DIR)/usr/lib/ -name '*.py' -exec rm {} \;
endif

Is that line really supposed to be there?

BR2_PACKAGE_PYTHON_DEV says:



"If enabled, development files (headers and static libpython) will be

                               installed on the target. "

It seems to me, if you have this disabled, you still might want the
basic python library installed on the target (especially if you set
BR2_PACKAGE_PYTHON_PY_ONLY=y)!

Maybe I'm missing something?

Thanks
Tobias
-- 
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com

[Buildroot] using linux 2.4 headers AND python

[Hamish Moffatt]

On Wed, Mar 25, 2009 at 11:35:46AM -0400, Tobias McNulty wrote:
> Tobias McNulty wrote:
> > and, sure enough, I don't see os.py anywhere on the filesystem.  I have
> > not looked at the python build output yet but I'll do that tomorrow when
> > I'm more awake.
> 
> Sure enough, the installer is installing all the .py files and then
> removing them again.  It appears the line at fault is the last one in
> the following section of python.mk
> 
> ifneq ($(BR2_PACKAGE_PYTHON_DEV),y)
>         rm -rf $(TARGET_DIR)/usr/include/python$(PYTHON_VERSION_MAJOR)
>         rm -rf
> $(TARGET_DIR)/usr/lib/python$(PYTHON_VERSION_MAJOR)/config
>         find $(TARGET_DIR)/usr/lib/ -name '*.py' -exec rm {} \;
> endif
> 
> Is that line really supposed to be there?

No it isn't, but you should also have the .pyc file (unless you have set
BR2_PACKAGE_PYTHON_PY_ONLY) so 'import os' will still work. You might
want to build python with logging and post the log here, ie

make python-dirclean python 2>&1 > pybuild.log


'svn blame' suggests this is my mistake. I use ..._PYC_ONLY so I didn't
notice.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

[Buildroot] using linux 2.4 headers AND python

[Tobias McNulty]

Hamish Moffatt wrote:
>> Is that line really supposed to be there?
> 
> No it isn't, but you should also have the .pyc file (unless you have set
> BR2_PACKAGE_PYTHON_PY_ONLY) so 'import os' will still work. You might
> want to build python with logging and post the log here, ie
> 
> make python-dirclean python 2>&1 > pybuild.log
> 
> 'svn blame' suggests this is my mistake. I use ..._PYC_ONLY so I didn't
> notice.

Cool, thanks for the quick reply.  I do have BR2_PACKAGE_PYTHON_PY_ONLY
selected, but only because that's the default.  Is PYC generally
smaller/faster?  A quick google seems to suggest that it's not much
faster..but maybe the difference is more noticeable on smaller embedded
machines.

Toby

-- 
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com

[Buildroot] using linux 2.4 headers AND python

[Peter Korsgaard]

>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:

Hi,

 Hamish> 'svn blame' suggests this is my mistake. I use ..._PYC_ONLY
 Hamish> so I didn't notice.

Will you fix it or should I?

-- 
Bye, Peter Korsgaard

[Buildroot] using linux 2.4 headers AND python

[Hamish Moffatt]

On Thu, Mar 26, 2009 at 07:57:42AM +0100, Peter Korsgaard wrote:
> >>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:
> 
> Hi,
> 
>  Hamish> 'svn blame' suggests this is my mistake. I use ..._PYC_ONLY
>  Hamish> so I didn't notice.
> 
> Will you fix it or should I?

I will.

The Python package needs a bit of work anyway. I am using 2.5 in my tree
(2.4 is in the repo). There should be a proper build for the host now
that we have $(HOST_DIR) too.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

[Buildroot] using linux 2.4 headers AND python

[Peter Korsgaard]

>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:

 >> Will you fix it or should I?

 Hamish> I will.

 Hamish> The Python package needs a bit of work anyway. I am using 2.5
 Hamish> in my tree (2.4 is in the repo). There should be a proper
 Hamish> build for the host now that we have $(HOST_DIR) too.

Exactly. I had it on my todo list, but feel free to do it if you have
time for it, I don't normally use Python.

-- 
Bye, Peter Korsgaard