Bering 3.1.1-beta2: e1000e, buildtool

[Juergen Northe]

Since obviously nobody has the driver of that nic, I tried to compile it by
myself with the buildtool environment.

Now I have the e1000e.o but the 'insmod e1000e' complains about unresolved
symbols called pm_qos_remove_management. So I suppose something went wrong
while compiling and now the driver is for 2.6 kernel and not 2.4.34-6 as
needed.

In the logfile i found something strage: I think it should not use my FC10
kernel-dir !!!???
---- SNIPP
/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src modules
make[2]: Entering directory `/usr/src/kernels/2.6.27.19-170.2.35.fc10.i686'
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/netdev.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/ethtool.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/param.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000_82571.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000_ich8lan.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000_80003es2lan.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000_mac.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000_nvm.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000_phy.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000_manage.o
  CC [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/kcompat.o
  LD [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000e.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000e.mod.o
  LD [M]
/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/e1000e-0.5.11.2/src/e1000e.ko
make[2]: Leaving directory `/usr/src/kernels/2.6.27.19-170.2.35.fc10.i686'
-------- SNIPP

I suppose that I have made an error in the buildtool.mk but can not find it.

I comment out the ./configure line since I do not have one there.

-------- SNIPP
#/home/remote/bering/src/bering-uclibc/buildtool/source/e1000e/buildtool.mk
include $(MASTERMAKEFILE)
MODUTILSDIR_DIR:=e1000e-0.5.11.2/src
$(MODUTILSDIR_DIR)/.source:
        zcat $(MODUTILS_SOURCE) | tar -xvf -
        touch $(MODUTILSDIR_DIR)/.source
source: $(MODUTILSDIR_DIR)/.source
$(MODUTILSDIR_DIR)/.build: $(MODUTILSDIR_DIR)/.source
        mkdir -p $(BT_BUILD_DIR)/modutils
        (cd $(MODUTILSDIR_DIR); \
                rm -rf config.cache; \
                CFLAGS="$(BT_COPT_FLAGS)" \
                CC=$(TARGET_CC) \
                LD=$(TARGET_LD) ); #\
#               ./configure --disable-root-check );
        make CFLAGS="$(BT_COPT_FLAGS)" CC=$(TARGET_CC) HOSTCC=$(TARGET_CC)
HOSTCFLAGS="$(BT_COPT_FLAGS)" LD=$(TARGET_LD) -C $(MODUTILSDIR_DIR)
        make CFLAGS="$(BT_COPT_FLAGS)" CC=$(TARGET_CC) HOSTCC=$(TARGET_CC)
HOSTCFLAGS="$(BT_COPT_FLAGS)" LD=$(TARGET_LD)
DESTDIR=$(BT_BUILD_DIR)/modutils -C $(MODUTILSDIR_DIR) install
        make CFLAGS="$(BT_COPT_FLAGS)" CC=$(TARGET_CC) HOSTCC=$(TARGET_CC)
HOSTCFLAGS="$(BT_COPT_FLAGS)" LD=$(TARGET_LD) DESTDIR=$(BT_STAGING_DIR) -C
$(MODUTILSDIR_DIR)        install
        touch $(MODUTILSDIR_DIR)/.build
build:  $(MODUTILSDIR_DIR)/.build


Can anyone give me a hint ?
Thank you in advance.

Juergen
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

[Martin Hejl]

Hi Juergen,

> In the logfile i found something strage: I think it should not use my FC10
> kernel-dir !!!???
indeed it shouldn't (at least, if it should run with Bering uClibc). But
since you didn't tell the makefile where the kernel sources reside, it
looked in the default location (where it found your Fedora kernel).

Where the kernel sources can be found is usually defined with the KSRC
variable - but some makefiles use something else (like LINUX) - the
readme that comes with the driver should have some info about that. If
not, you'll have to take a look at the makefile and find out how to make
it look in the kernel dir for Bering uClibc.

> I suppose that I have made an error in the buildtool.mk but can not find it.
Well, the first step should be to copy a buildtool.mk/cfg that fits your
needs. Modutils wasn't a terribly good choice, something that produces a
module, rather than user-space binaries, would have worked better.

Have a look at the setup for the r1000 driver - it's nice and clean, and
should work well as a base to work from

http://leaf.cvs.sf.net/viewvc/leaf/src/bering-uclibc/contrib/r1000/buildtool.mk?revision=HEAD&view=markup

Oh - you should also take the time to rename the variables (and
directories) to something that represents your driver (e1000 for
example) - it's less confusing that way, and if it's done right from the
start, you avoid having to clean things up later.

I hope that helps

Martin

P.S. You might get more responses posting buildtool related questions on
the leaf-devel list, since it's more of a developer issue (then again, I
guess all the people who answer questions on leaf-devel are also
subscribed to leaf-user, so it probably makes no difference other than
keeping things a little more organized).

------------------------------------------------------------------------------
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@...
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/