Hi There! On a PowerPC machine, I 've tried to build the latest iproute2 port with the current gcc-4.2.0 (which works pretty good, btw). It builds fine, but =======> ERROR: Footprint mismatch found: MISSING -rwxr-xr-x root/root sbin/tc MISSING -rwxr-xr-x root/root usr/lib/tc/q_netem.so tc ist missing. Which is the traffic control settings manipulator. I guess it was just skipped, propably because of my minimal kernel configuration (2.6.21-rc5-something). Am I right? Or are there any other dependencies I missed there? What minimum settings do I need to enable in the kernel to get it built? Thanks, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com
Hi Clemens, When I get footprint mismatch errors, I just go into the directory of the port, eg, /usr/ports/opt/<NAME HERE> and issue the pkgmk command with the -if switch to ignore the footprint. pkgmk -if Then I use the normal pkgadd command to install the port. Hope this helps!
Joshua Higgins ha scritto:
Hi Clemens,
When I get footprint mismatch errors, I just go into the directory of the port, eg,
/usr/ports/opt/<NAME HERE>
and issue the pkgmk command with the -if switch to ignore the footprint.
pkgmk -if
Then I use the normal pkgadd command to install the port.
Hope this helps!
this is a workaround to the footprint mismatch error, but not the solution to the problem. The reason why /sbin/tc hasn't built is probably due to the kernel configuration. Regards -- bisco at cruxppc dot org CRUX PPC Team! [http://cruxppc.sunsite.dk]
Hello, bisco. On Tue, 22 May 2007 09:56:46 +0200 bisco <bisco@cruxppc.org> wrote:
The reason why /sbin/tc hasn't built is probably due to the kernel configuration. ...or an incompatible headers version installed?[1] And/or might be PowerPC specific thing. Anyway, a full build log is a first thing to look at.
[1] https://crux.nu/bugs/?do=details&task_id=133&pagenum=3 -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta
Hi, Mikhail! Mikhail Kolesnik schrieb:
Hello, bisco. bisco <bisco@cruxppc.org> wrote:
The reason why /sbin/tc hasn't built is probably due to the kernel configuration. ...or an incompatible headers version installed?[1] And/or might be PowerPC specific thing. Anyway, a full build log is a first thing to look at.
Thank you for that link. I have still quite old 2.6.13 kernel headers installed. Well, I am about to replace them as soon as possible. Is it a good idea to recommend our users to do a make headers_install along with every new kernel installation (on "production" machines)? Greets, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com
Hello Clemens, as far as i remember, you are only supposed to update the kernel-headers in your /usr/include directories, when upgrading glibc. more specific information and background can be found on www.linuxfromscratch.org, the book documents the whole process of building a linux system from scratch and gives many helpfull hints on dependency and compatibility issues on base installs (kernel, glibc, gcc, binutils and other lowlevel stuff) regards /HJM ----- Original Message ----- From: "Clemens Koller" <clemens.koller@anagramm.de> To: "Mikhail Kolesnik" <mike@openbunker.org> Cc: <crux@lists.crux.nu> Sent: Wednesday, May 23, 2007 2:51 PM Subject: Re: iproute2 /bin/tc not built - why?
Hi, Mikhail!
Mikhail Kolesnik schrieb:
Hello, bisco. bisco <bisco@cruxppc.org> wrote:
The reason why /sbin/tc hasn't built is probably due to the kernel configuration. ...or an incompatible headers version installed?[1] And/or might be PowerPC specific thing. Anyway, a full build log is a first thing to look at.
Thank you for that link. I have still quite old 2.6.13 kernel headers installed. Well, I am about to replace them as soon as possible.
Is it a good idea to recommend our users to do a make headers_install along with every new kernel installation (on "production" machines)?
Greets, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
Hello, Hans-Joachim. On Wed, 23 May 2007 15:01:44 +0200 "Hans-Joachim Michl" <hmichl@yawsp.de> wrote:
Is it a good idea to recommend our users to do a make headers_install along with every new kernel installation (on "production" machines)? [..] as far as i remember, you are only supposed to update the kernel-headers in your /usr/include directories, when upgrading glibc.
And this brings a broader problem: AFAIK, we have no reliable/documented way to safely rebuild toolchain. Looking from the point of distro's long release cycle, we might face a problem trying to upgrade tools like iproute2 or ipsec-tools. -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta
Hello, Mikhail! Mikhail Kolesnik schrieb:
as far as i remember, you are only supposed to update the kernel-headers in your /usr/include directories, when upgrading glibc.
And this brings a broader problem: AFAIK, we have no reliable/documented way to safely rebuild toolchain. Looking from the point of distro's long release cycle, we might face a problem trying to upgrade tools like iproute2 or ipsec-tools.
Yes, that seems to be a never ending story. In ix86 it became more simple to bootstrap binutils/glibc/gcc/kernel and friends. It's also not such a big deal to just upgrade glibc in a running system... But on some embedded systems it's just a painful task to go thru the first LFS Chapter plus ton's of bugfixes and patches. I am still not sure if I'll stay with the latest developemnt snapshots of the native/cross-toolchain(s) to get more support/immediate feedback of the developers or go with the latest stable series plus a varying selection of patches. It would be fun to assemble a CCFS (Crossplatform Crux From Scratch) skript. My idea/wish/dream is to get to a point where an automated tool monitors toolchain changes and does a full automatic bootstrap of the toolchain plus some tests (from the Linux Test Project). It should also spit out a ISO Image if the build was successful. I would offer a server for free to do that. Well... sometimes, dreams come true. ;-) Greets, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com
I just tried installing iproute2 on my i686 pc, and tc works with the defualt kernel built, but it isn't really needed unless you want to change the traffic control settings, iproute2 works anyway.
Ok, sorry about last posts. Anyway, I've found the answer. To get tc to build properly, you need to enable QoS support and/or QoS Fair queueing in the kernel configuration.
Hi, Joshua!
Ok, sorry about last posts.
Don't worry, I expected that... ;-) I am getting used to ignore footprint mismatches, too. But I sometimes try to understand the dependencies, at least on my development machine.
Anyway, I've found the answer. To get tc to build properly, you need to enable QoS support and/or QoS Fair queueing in the kernel configuration.
Thank you, I'll enable that next time! Greets, -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com
participants (5)
-
bisco -
Clemens Koller -
Hans-Joachim Michl -
Joshua Higgins -
Mikhail Kolesnik