SEO

Howdy all,

Recently, I've attempted to build all of kde 3.1.3 on a test bed PII
450-> (Kernel 2.4.22). Aside from a few user mistakes done prior to
compile time, the build went rather well (about 20+ hours well).
When I compared file sizes of my build (with heavy optimizations)
versus the stock kde 3.1.3 files supplied via the patches directory,
I noticed a size disparity in kdemultimedia and kdeaddons. I also
noticed some of the functionality in the kde sound system was gone.
There were no mixer controls and I also saw "can't find sound-slot-0
blah" in the sys logs again. Not only that, but many of the binaries
were absent from my build.

To get to the point, one problem was in "kdemultimedia" inside the
"kaudiocreate" directory. kaudiocreate wasn't being built properly
and wacked the rest of the build script. This error message was
responsible for killing the build: (Wrapped)

###
-new -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -MT cdconfigimp.o -MD
-MP -MF ".deps/cdconfigimp.Tpo" \
-c -o cdconfigimp.o `test -f 'cdconfigimp.cpp' || echo
'./'`cdconfigimp.cpp; \
then mv ".deps/cdconfigimp.Tpo" ".deps/cdconfigimp.Po"; \
else rm -f ".deps/cdconfigimp.Tpo"; exit 1; \
fi
In file included from /usr/include/linux/cdrom.h:14,
from cdconfigimp.cpp:78:
/usr/include/asm/byteorder.h:38: syntax error before `(' token
/usr/include/asm/byteorder.h:42: '__u64' is used as a type, but is
not defined
as a type.
/usr/include/asm/byteorder.h:43: parse error before `}' token
/usr/include/asm/byteorder.h:44: syntax error before `.' token
/usr/include/asm/byteorder.h:50: syntax error before `.' token
/usr/include/asm/byteorder.h:51: syntax error before `.' token
/usr/include/asm/byteorder.h:52: parse error before `:' token
In file included from
/usr/include/linux/byteorder/little_endian.h:11,
from /usr/include/asm/byteorder.h:65,
from /usr/include/linux/cdrom.h:14,
from cdconfigimp.cpp:78:
/usr/include/linux/byteorder/swab.h:199: syntax error before `('
token
/usr/include/linux/byteorder/swab.h:209: syntax error before `('
token
/usr/include/linux/byteorder/swab.h:213: `__u64' was not declared in
this scope
/usr/include/linux/byteorder/swab.h:213: `addr' was not declared in
this scope
/usr/include/linux/byteorder/swab.h:214: variable or field
`__swab64s' declared
void
/usr/include/linux/byteorder/swab.h:214: `__swab64s' declared as an
`inline' variable
/usr/include/linux/byteorder/swab.h:214: syntax error before `{'
token
cdconfigimp.cpp:81: parse error before `}' token
make[1]: *** [cdconfigimp.o] Error 1
make[1]: Leaving directory
`/root/adev2/kdemultimedia-3.1.3/kaudiocreator'
make: *** [all-recursive] Error 1
###

Interesting. I also tried a test build of kmultimedia 3.1.4 and I
ended up with this: (wrapped)

###
-new -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -MT cdconfigimp.o -MD
-MP -MF ".deps/cdconfigimp.Tpo" \
-c -o cdconfigimp.o `test -f 'cdconfigimp.cpp' || echo
'./'`cdconfigimp.cpp; \
then mv ".deps/cdconfigimp.Tpo" ".deps/cdconfigimp.Po"; \
else rm -f ".deps/cdconfigimp.Tpo"; exit 1; \
fi
In file included from /usr/include/linux/cdrom.h:14,
from cdconfigimp.cpp:79:
/usr/include/asm/byteorder.h:38: syntax error before `(' token
/usr/include/asm/byteorder.h:42: '__u64' is used as a type, but is
not defined
as a type.
/usr/include/asm/byteorder.h:43: parse error before `}' token
/usr/include/asm/byteorder.h:44: syntax error before `.' token
/usr/include/asm/byteorder.h:50: syntax error before `.' token
/usr/include/asm/byteorder.h:51: syntax error before `.' token
/usr/include/asm/byteorder.h:52: parse error before `:' token
cdconfigimp.cpp:82: parse error before `}' token
make[1]: *** [cdconfigimp.o] Error 1
make[1]: Leaving directory
`/root/adev3/kdemultimedia-3.1.4/kaudiocreator'
make: *** [all-recursive] Error 1
###

Since all of this hath taxed my tired newb brain, I'd rather not
make any assumptions. Can someone here give me an idea of what might
be going on?

Anyway, I did seemingly get around this. I noticed a disparity in
the kernel 2.4.22/21 include "byteorder.h" file as opposed to the
file in 2.4.20. This newbie simply switched the files (temporarily) and
kdemultimedia (all of it) compiled without a single complaint.
Whether or not this was a good idea has yet to be determined.

Any suggestions or ideas appriciated...

Thanks,

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On 25 Oct 2003 00:30:35 GMT, Scott <scott421@bellsouth.net> wrote:
> Since all of this hath taxed my tired newb brain, I'd rather not
> make any assumptions. Can someone here give me an idea of what might
> be going on?

Yes - the people in a KDE mailing list or a KDE newsgroup.

Google might know, too, but I haven't asked her, nor so I plan to
tonight. We had a spat earlier, and I don't think she wants to talk to
me right now.

--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/md2Qhm6KEoOOAe0RAp1QAKCUyI09yKQKNmv2uvyeM4eKH4g8wA CgsnWU
Wyp9MoB9BTeCYC1SH+JEtfc=
=1Efp
-----END PGP SIGNATURE-----

On Fri, Oct 24 2003, in alt.os.linux.slackware,
AthlonRob <junkmail@axpr.net> wrote:

> NotDashEscaped: You need GnuPG to verify this message
>
> On 25 Oct 2003 00:30:35 GMT, Scott <scott421@bellsouth.net> wrote:
>> Since all of this hath taxed my tired newb brain, I'd rather not
>> make any assumptions. Can someone here give me an idea of what
>> might be going on?
>
> Yes - the people in a KDE mailing list or a KDE newsgroup.

Joost already mentioned doing this and I plan on it. But not before
exhausting all possibilities in aols.

> Google might know, too, but I haven't asked her, nor so I plan to
> tonight. We had a spat earlier, and I don't think she wants to
> talk to me right now.

Google *always* knows. Just a matter of getting ones search terms
restricted to the point of usability. Basically, that was all that I
was hoping for.