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
All,
Built and installed knemo, my favorite network monitor. The first thing I
notices was there was no menu entry created? IIRC there was always a launcher.
Not a huge problem, 'kcmshell kcm_knemo' fires the config right up. Configure it
to taste, set nettools backend to sys and --- nothing shows up in the systray?
Tweak config, try NetTools backend, delete eth0 and recreate, still - no knemo
in systray. Hmm - anyone else see this?
[ ] hide when not connected - unchecked :)
--
David C. Rankin, J.D.,P.E.
All,
This may be a bug in the kbarcode database connect code. I configured mysql
and tested kbarcode. The database connect failed using the TQMYSQL3 driver
(selected in kbarcode settings) Has anyone got it working in R14? The error
received was:
Unable to open database: kbarcode
could not connect to server: Connection refused Is the server running on host
"localhost" (::1) and accepting TCP/IP connections on port 5432? could not
connect to server: Connection refused Is the server running on host "localhost"
(127.0.0.1) and accepting TCP/IP connections on port 5432?
The user and pass are properly configured in mysql. I also tested my suse kde3
install and setup connected with the 'QMYSQL3' driver without any problems,
installed the tables and added the example data.
Thoughts? Anybody tested this with the 'TQMYSQL3' driver? Seems the 'T' driver
prefix may be a bit nebulous...
--
David C. Rankin, J.D.,P.E.