All,
The current mlt++ source Makefile requires that the 'test' directory be
compiles as part of the build. This fails on Arch. I have disabled the build
of the 'test' dir files with:
sed -i '/\$(MAKE) -C test \$@/d' Makefile
Is there any reason they should be built by the current Makefile to begin
with? Isn't that something that is normally done by the user AFTER the package
is installed? Since the 'test' Makefile requires -lmlt++ and that lib isn't
installed until the package is installed - this will cause a build failure
every time.
--
David C. Rankin, J.D.,P.E.
Building kstreamripper is broken because the python build script can't parse the new TDE versioning scheme and looks for kde-config rather than tde-config.
I tried fixing things but fell short and filed bug report 946:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=946
I don't think the changes need be prolific. If you have any python experience you probably can make the changes in short order.
As always am I ready to test any patches.
Thanks!
Darrell
All,
GIGO right - computers, given the same input should produce the same output
every time. If it's garbage in it's garbage out.
The build of sip4-tqt seems to violate that adage. When attempt to build
sip4-tqt (the first time/randomly), I get a failure:
gcc -c -march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -I/usr/include/tqt
-I/opt/trinity/include -I/opt/tqt3/include -O2 -w -DNDEBUG -I. -o parser.o parser.c
lex -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -t lexer.l > lexer.c
/usr/bin/flex: Unrecognized option `W'
Try `flex --help' for more information.
make[1]: *** [lexer.c] Error 1
make[1]: Leaving directory `/build/src/sipPy3/sipgen'
make: *** [all] Error 2
The only 'W' that could be causing the error is the LDFLAGS string
'-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu', but that hasn't
caused a problem before so I just issue the build command again - and it builds
without issue - WTF?
Looking at the lex command above I see:
lex -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -t lexer.l > lexer.c
That doesn't seem right. I don't know lex from fred, passing 'lex ${LDFLAGS}
-t lexer.l > lexer.c' doesn't seem right because there is no
'-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu' c syntax that I
know of :)
Has anyone else seen this spurious behavior? I kills rebuilds when it causes
sip build failures
I haven't changed a thing, and I get different results.
The build is simple:
<snip>
cd ${srcdir}
## copy source for Python build
cp -r ${pkgbase#*-} sipPy3
## Python version
msg "Running python configure.py (python3 based sip)...."
cd ${srcdir}/sipPy3
python configure.py CFLAGS="${CFLAGS}" LFLAGS="${LDFLAGS}"
msg "Building - tde-sip (python3 based sip)..."
make
## Python2 version
msg "Running python2 configure.py (sip4-tqt)...."
cd ${srcdir}/${pkgbase#*-}
python2 configure.py CFLAGS="${CFLAGS}" LFLAGS="${LDFLAGS}"
msg "Building - ${pkgbase}..."
make
}
Any thoughts?
--
David C. Rankin, J.D.,P.E.
Tim, All,
Do we want to flag packages that still have old build files in them? Look at
kima - it still has somebody's old config.log in the kima dir. Etherpad issue?
--
David C. Rankin, J.D.,P.E.
Tim, Slavek
tsak/tdmtsak are still broken and taking almost 100% of the cpu when TDM is
used as the login manager. This is with 'todays' (03/29) build from the GIT tree:
http://www.3111skyline.com/dl/dt/trinity/ss/tsak-96-cpu.jpg
I thought this was fixed??
--
David C. Rankin, J.D.,P.E.
I would like to update branding issues in all of the What's This and Tooltip text strings. Primarily changing KDE -> TDE.
A challenge is many of the text strings are multiple lines. A simple find/sed one-liner will be insufficient.
The What's This strings are contained in TQString functions and end with the traditional semi-colon. Additional What's This strings are in XML files enclosed in <whatsthis> and </whatsthis> tags.
The tool tips are embedded in i18n functions.
I'm no expert with awk or perl and I'm guessing either is better for addressing this challenge.
A good way for me to learn some basics about awk or perl is to update these text strings.
I would appreciate some awk/perl tips or pointers for approaching this mini project.
Thanks!
Darrell