[Solved] dvbcut compile problems - New PKGBUILD fix!

Anyone using dvbcut? The aur version won't compile, nor the tar package version from sourceforge nor the svn version (170). It all seems to boil down to qt3/qt4 mismatches. I have both versions installed yet I get; configure: error: Qt library not found
I even tried compiling the latest Ubuntu version with same results (desperation?)
I know it's an old app but it did the job very well of editing mpg/m2t files. I do not like avidemux!
Fedora and Ubuntu seem to have '-dev' packages which solves these kinds of problems. And hacking those libraries manually is too tricky to be worth it. Is there an Arch solution somewhere?
Last edited by swanson (2011-09-25 14:49:02)

Seems that this modified PKGBUILD works:
# Contributor: sp42b <sp42b|a_t|gmx.net>
# Contributor: AndyRTR <[email protected]>
## Contributor: swanson
pkgname=dvbcut
pkgver=0.6.2
pkgrel=1
pkgdesc="Qt3 application for cutting parts out of DVB streams"
arch=('i686' 'x86_64')
url="http://dvbcut.sourceforge.net/index.html"
license="GPL"
depends=('qt3' 'libao' 'libmad' 'a52dec')
optdepends=('mplayer: for video playback inside of DVBCUT')
source=(https://launchpad.net/~frafu/+archive/ppa/+files/dvbcut_0.6.2-0ppa%7Esvn178%7Enatty1.tar.gz)
md5sums=('cc49cd50dd44184d3db6125297a92ab5')
build() {
cd ${srcdir}/dvbcut-0.6.2-0ppa~svn178~natty1
msg "${srcdir}/dvbcut-0.6.2-0ppa~svn178~natty1"
autoconf
./configure --prefix=/usr
make
install -Dm755 ${srcdir}/dvbcut-0.6.2-0ppa~svn178~natty1/bin/dvbcut ${pkgdir}/usr/bin/dvbcut
install -Dm644 ${srcdir}/dvbcut-0.6.2-0ppa~svn178~natty1/dvbcut.1 ${pkgdir}/usr/share/man/man1/dvbcut.1
install -Dm644 ${srcdir}/dvbcut-0.6.2-0ppa~svn178~natty1/dvbcut.desktop ${pkgdir}/usr/share/applications/dvbcut.desktop
install -Dm644 ${srcdir}/dvbcut-0.6.2-0ppa~svn178~natty1/dvbcut.svg ${pkgdir}/usr/share/pixmaps/dvbcut.svg
OK for the AUR?
Last edited by swanson (2011-08-22 06:17:04)

Similar Messages

[Solved] Yaourt (warning:problem in pkgbuild.sh library)

Что это за ошибка, и как ее исправить?
После warning:problem in pkgbuild.sh library, пишет:
/usr/local/lib/yaourt/util.sh line 164: package-query: команда не найдена.
Ошибка появляется после обновления яорта, или после написания команды яорта установить что-то, например: yaourt -S broadcom-wl.
Last edited by anp (2012-11-09 11:21:02)

Trilby wrote:If google-translate was right, you need the following:
INSTALL: https://aur.archlinux.org/packages/package-query/
Спасибо за подсказку.
Скачал package-query, перенес его в папку tmp и из консоли начал устанавливать (по инструкции в файле install)
cd /tmp/pacage-query-1.1
./configure
make
make: Не заданы цели и не найден make-файл.
google-translate:
Thanks for the tip.
I downloaded the package-query, transferred it to the tmp folder and started from the console to install (the instructions in the file install)
cd / tmp/pacage-query-1.1
. / configure
make
make: do not set targets and not found make-file.

[Solved] vDrift compile problem

Tried to install vdrift from AUR but the pkgbuild is out of date. But I'd really like to get it going (I like this program) and thought someone just might know what to do. I think its missing a dependency or two and fails on the checks:
You do not have the GL/glew.h headers installed. Exiting.
Google-fu'd and only found one reference that says that libsdl must be install. I know that Debian's and Arch's naming differ but I can't figure out what this app may be in Arch. Here's what i got installed:
extra/sdl 1.2.13-3
extra/sdl_gfx 2.0.18-1
extra/sdl_image 1.2.7-1
extra/sdl_mixer 1.2.8-3
extra/sdl_net 1.2.7-2
extra/sdl_ttf 2.0.9-1
Any ideas?
Last edited by Gen2ly (2009-05-29 08:21:48)

The include file in question is provided by extra/glew:
pacman -S glew

E 71 turkey languange fixed problems new software

e 71 new software fixed problems turkey languange HELP ME ?
501.21.001
10-08-2010
RM-346
Nokia E71-1 (344.09)

That might occur sometimes with firmware update.
You can do one of 2 things:
1) to wait , and reinstall the firmware again, because sometimes Nokia add language packs according to country you are using the phone from.
2) to go to the nearest Nokia Care Center ,and ask them to install the turkey language pack.
Phones I bought from 1st till now:
3210 / 3310 / 3410 / 6310 / 6600 / 6020 / N72 / E51 / X2-00 / 5310 xpress Music / E90 Communicator
If you like my post or it helped you, Give me Kodo

A java virus disabled the click + at the left to open new tab. I have reinstalled firefox but the problem is not fixed. what do i do to fix this?

A java virus disabled the click + at the left to open new tab. I have reinstalled firefox but the problem is not fixed. what do i do to fix this?
admins of forum feel free to edit post.

Try disabling the Ask Toolbar extension.

[svn:fx-trunk] 11707: Fix incremental compilation problem with styles.

Revision: 11707
Author:   [email protected]
Date:     2009-11-12 10:52:49 -0800 (Thu, 12 Nov 2009)
Log Message:
Fix incremental compilation problem with styles.
QE notes: None.
Doc notes: None.
Bugs: SDK-24173
Reviewer: Paul
Tests run: checkintests
Is noteworthy for integration: No.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24173
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StylesContainer.java

You have used elements like header, footer, footer1 and nav without using the correct DOCTYPE declaration. Replace the first line of your code with
<!doctype html>
Also have a look here for other problems http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fhome.surewest.net%2Fstorytales%2F test%2Fforposting.html
After the above has been fixed, please come back here to fix the remaining problem(s)
Gramps

[SOLVED]openstudio is a new AUR package, requesting review of PKGBUILD

Hi,
I have been working on a simple desktop environment for Arch Linux, called OpenStudio.se . This is the first time I have made a PKGBUILD and it would be great if anyone with some more experience could help me verify that the PKGBUILD is correct. I have tested it on both x86_64 and x86 systems and it works well and the package installs correctly with pacman.
If you want to check out the desktop environment, visit www.openstudio.se
BR
Mikael
Here is my PKGBUILD :
# Maintainer: Mikael Nordvall <[email protected]>
pkgname=openstudio
pkgver=0.4
pkgrel=1
pkgdesc="Scripts to install and configure a simple, lightweight desktop environment for Arch Linux"
arch=(any)
url="http://www.openstudio.se/de/"
license=('GPL3')
source=(http://www.openstudio.se/de/source/$pkgname.tar.gz)
md5sums=('dc085cf28b74a541833a680603fa85be') #generate with 'makepkg -g'
package() {
mkdir $pkgdir/etc
mkdir $pkgdir/etc/openstudio
mkdir $pkgdir/usr
mkdir $pkgdir/usr/bin
mkdir $pkgdir/usr/share
mkdir $pkgdir/usr/share/man
mkdir $pkgdir/usr/share/man/man1
cp -r $srcdir/$pkgname $pkgdir/usr/share/
cd $pkgdir/usr/share/$pkgname/
cp ./scripts/openstudio $pkgdir/usr/bin/
cp ./library/manpage/openstudio.1.gz $pkgdir/usr/share/man/man1/
Last edited by zkeng (2011-10-09 10:27:25)

Thank you very much for the input Stefan. I will update the PKGBUILD according to your suggestions.
About the empty dir /etc/openstudio
The openstudio package contains a system configure script. When executed this script will set-up some global config files (shared for all users) in this dir. The reason why I created it already during installation is because I do want it to be removed if you decide to remove the openstudio package. The reason why it is empty at the beginning is because I do not want to over-write its content when openstudio package is upgraded.
Maybe there is another standard way of solving this kind of issue, but to avoid the error you mentioned about an empty dir I made sure an info file is copied to the dir during install.
New PKGBUILD (with new md5sum) :
# Maintainer: Mikael Nordvall <[email protected]>
pkgname=openstudio
pkgver=0.4
pkgrel=1
pkgdesc="Scripts to install and configure a simple, lightweight desktop environment for Arch Linux"
arch=(any)
url="http://www.openstudio.se/de/"
license=('GPL3')
source=(http://www.openstudio.se/de/source/$pkgname.tar.gz)
md5sums=('4f9dec211a1b082d91251fa0e73810db') #generate with 'makepkg -g'
package() {
install -d $pkgdir/usr/share
cp -r $srcdir/$pkgname $pkgdir/usr/share/
cd $pkgdir/usr/share/$pkgname/
install -Dm755 ./scripts/$pkgname $pkgdir/usr/bin/$pkgname
install -Dm644 ./library/config/readme_etc_$pkgname \
$pkgdir/etc/$pkgname/readme_etc_$pkgname
install -Dm644 ./library/manpage/$pkgname.1.gz \
$pkgdir/usr/share/man/man1/$pkgname.1.gz
Last edited by zkeng (2011-10-08 18:48:59)

I cant find my all files in new version and older version is better than new and fix this problem....!

I can't find my all PDF in new version and older version is better than new and fix this problem as soon as possible....!

Hi Manoj,
what exact problem are you facing? Are you unable to locate your pdf files?
Regards,
Rahul

Will a new computer fix the problem?

I currently have a Windows XP system from appx 2004 with PSE 3.0 on it. PSE 3.0 is no longer responding when I try to open the browser or editor or anything! the computer seems to be having other issues as well so I think its time to upgrade to a newer computer. When I last backed up my photos (44,000+) to an external drive, the PSE 3.0 was working fine. If I get a new computer and install PSE 3.0 on the new computer and use my backup to load all my photos to the new computer.. will the PSE 3.0 load with all of the original tags from the photo browser?

I have never performed a backup with video files, as I don't have any.
Nevertheless, based on the way the PSE Organizer works, I am relatively certain that the tags for videos are included in the backup (as well as the tags for photos). I'm also relatively certain that both photos and videos are included in the backup. (Note: I am referring to backups made via the Organizer command File->Backup Catalog)
But the only way to know for sure is to cross your fingers and try it.
Best to start a new thread since your question has nothing to do with the original topic (will a new computer fix the problem)

Re: [iPlanet-JATO] sp3 jsp compiler problem

Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text
substitution situations, and as a completely independent tool its use is not
restricted to migration situations (or file types for that matter).
Second, I sympathize with the unfortunate trouble you are experiencing due to
Jasper's (perhaps more strict) compilation, but in what way did the iMT
automated translation contribute to these inconsistencies that you cited?
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a
translation situation, the only way "OnClick" would have been introduced was if
it had been part of the pre-existing project's "extraHTML" (which was written
by the original customer and just passed through unchanged by the iMT) or if it
was added manually by the post-migration developer.
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be
similar to the OnClick situation described above?
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no
equivalent in the NetDynamics world, so any content tags in your code must have
been introduced by your developers manually. Its a shame that jasper is so
particular, but the iMT could not help you out here even if we wanted to. The
constants that are used by the iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can see, the
only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174144234026000079108238073194105057099246073154180137239239223019162">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
[Non-text portions of this message have been removed]

Thanks a lot Matt and Mike for your prompt replies.
I agree completely that iMT doesn't introduce the inconsistencies.
About the three cases I mentioned, the third one happens only in
manually created JSPs. So it has nothing to do with iMT. The first
two are mainly due to the existing HTML code, as you rightly pointed
out.
The reason I made the suggestion is since we know that case 1 and 2
won't pass the japser compiler in sp3, we have to do something about
it. The best place to do this, in my mind, is iMT. Of course, there
might be some twists that make it impossible or difficult to do this
kind of case manipulation or attribute discard.
Weiguo
--- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
Weiguo,
First, Matt is correct, the regular expression tool is perfect for general text substitution situations, and as a completely independent
tool its use is not restricted to migration situations (or file types
for that matter).
>
Second, I sympathize with the unfortunate trouble you are experiencing due to Jasper's (perhaps more strict) compilation, but
in what way did the iMT automated translation contribute to these
inconsistencies that you cited?
>
1. Changed the case of the tag attribute to be the same as what's
defined in tld.
example: changed OnClick to onClick
The iMT does not generate any OnClick or onClick clauses per se. In a translation situation, the only way "OnClick" would have been
introduced was if it had been part of the pre-existing
project's "extraHTML" (which was written by the original customer and
just passed through unchanged by the iMT) or if it was added manually
by the post-migration developer.
>
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.Can you give soem examples? Is there a definite pattern? Again, this might be similar to the OnClick situation described above?
>
>
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
Again, the content tag would never have been generated by the iMT. There was no equivalent in the NetDynamics world, so any content tags
in your code must have been introduced by your developers manually.
Its a shame that jasper is so particular, but the iMT could not help
you out here even if we wanted to. The constants that are used by the
iMT are defined in
com.iplanet.moko.jsp.convert.JspConversionConstants. From what I can
see, the only situation of a closing tag with any space in it is
public static final String CLOSE_EMPTY_ELEMENT = " />";
But that should not cause the type of problem you are referring to.
Mike
----- Original Message -----
From: Matthew Stevens
Sent: Thursday, September 06, 2001 10:16 AM
Subject: RE: [iPlanet-JATO] sp3 jsp compiler problem
Weiguo,
Others will chime in for sure...I would highly recommend the Regex Tool from
the iMT 1.1.1 for tackling this type of problem. Mike, Todd and myself have
posted to the group (even recently) on directions and advantages of creating
your own RULES (rules file) in XML for arbitary batch processing of source.
>
matt
-----Original Message-----
From: weiguo.wang@b...
[mailto:<a href="/group/SunONE-JATO/post?protectID=125056020108194190033029175101192165174048139046">weiguo.wang@b...</a>]
Sent: Thursday, September 06, 2001 12:25 PM
Subject: [iPlanet-JATO] sp3 jsp compiler problem
Matt/Mike/Todd,
We are trying to migrate to sp3 right now, but have had a lot of
issues with the new jasper compiler.
The following workaround has been employed to solve the issues:
1. Changed the case of the tag attribute to be the same as
what's
defined in tld.
example: changed OnClick to onClick
2. Removed attributes which are not defined in tld.
example: escape attribute only defined in three tags
but in some pages, it's used although it's not defined as an
attribute
of certain tags. The jasper compiler doesn't like it.
3. In an end tag, there can't be any space.
example: </content > doesn't work. </content> works.
As I see it, we have two options to go about solving this problem:
>>
1. Write a script which will iterate through all the jsp files and
call jspc on them. Fix the errors manually when jspc fails. Jspc will
flag the line number where an error occurs.
2. Write a utility which scans the jsp files and fix the errors when
they are encountered. We should define what's an error and how to
correct it. It's best if we combine this with solution 1 since we
might miss an error condition.
Actually, there might be another option, which is seeking help from
you guys since you have better understanding of JATO and iAS. Can you
do anything to help us?
We would be happy to hear your thoughts.
At last, I would like to suggest modifying the moko tool so that
these rules are enforced and the generated JSPs work with the new
compiler. This is for the benefit of any new migration projects.
Thanks a lot.
Weiguo
[email protected]
Choose from 1000s of job listings!
[email protected]
Service.
>
>
>
[Non-text portions of this message have been removed]

Avoid MathScipt Comments in EXE, Build & Run Problems - NI Please Fix these Bugs!

Hello,
After 4 days of intensive work, I have finally found the solution for two major MathScript Problems:
1) Mathscript Comments are included in your EXE File !!
    - Yes, if you do not watch your steps, the EXE will include all your % Mathscript Comments!
2) Problems building, but even worse: An app that builds with NO Error and NO Warnings will not RUN and creates the following misleading Erro Message:
    "The VI is not Executable. The full development version of LabView is required to fix the errors"
    With absolutely NO hint to what VI have the problem.
I have made myself an internal note how to avoid this problem. I am using LabView 2009, 2010 DS1 Release (I think this is 9.01) under WInXP SP2.
Rather than retyping everything, I will post the full text of my Notes below. I also mention several other LV BUG in this note, so pleae read carefully.
One is the TagSrv Error that occurs in LabView 2009 if I programatically deploy Shared Variables under the WinXP Development Environment. After this problem has occured, it will occur every time I restart XP, and in essense I have to restore to before I did this (thanks Nortong Ghost !!!).
Below you can find the full unabridged version of my Build, Run and Bug Notes for LV 2009 / 2010 DS1 (9.01). Hope they can be helpful to my fellow LabView programmers!
2010-07-03:
Building under LabView 2009 / 2010 DS1 Release (version 9.01)
Follow the steps below:
a) To successfully build an EXE that also runs
b) Avoid that MathScript Comments are included in the EXE !!!!!!!!!!!!!!!!
Before Building:
I) Recompile All by pressing Ctrl+Shift and pressing the RUN button on the Application_References.vi
   Then Save All (about 1200 Vis are saved)
II) Make Sure that NO User Defined Mathscript (and Mathscript Nodes?) define Empty Functions:
    This seemed to cause the following problem with the built EXE: The main VI will be broken, and a dialog reports:
    "The VI is not Executable. The full development version of LabView is required to fix the errors"
    MathScitp BUG: Empty Functions causes no Build Errorm but RUN Error:
    The following User Defined MathScript .m files are candidates:
    log_write() and log_clear() whith do_log_write() and do_log_clear() commented out, these functions are empty.
    When calls to log_write() and log_clear() where removed, the problem above vanished !
Building the EXE:
1) Additional Exclusions:
-"Disconnect type definitions": YES
- "Remove unused polymorphic VI instantces": YES
- "Remove unused members of project libraries": NO (do not know if this is important)
2) Advanced:
- Enable Debugging: "NO"
3) Mathscript BUG: The Application Builder Includes ALL MathScript Comments in the EXE if you use the New Build File Layout:
   IMPORTANT !!!!!!!!!!!!!
   Advanced:
   "Use LabView 8.x file layout": YES !!!!!!!
   Using the new layout, causes ALL COMMENTS FROM USER DEFINED MATHSCRIPT .M FILES TO BE INCLUDED IN THE .EXE !!!!!!!
4) BUG: DSC Reference Problem in LabView 2010 DS1 release:
   In VI Deploy_Shared_Variables.vi we deploy alle Shared Variables using the "Deploy Libraries.vi" which is a part of the DSC option.
   As long as only deploying of Variables is used, using this VI should NOT require any DSC Runtime license.
   We have used this before with no compilation problems.
   However, starting with LV 2009 SP1 (or was it the DS1 2010 upgrade) LV will start nagging us to resolve references to tens of VIs
   in the DSC lib file ! Solution: Used press "Stop" on the dialog, and the Build will succeed and the EXE will work !
   Optionally, we could use the following Invoke node for the deployment:
   (see: http://digital.ni.com/public.nsf/allkb/04D9A85B6967EE87862571140065EEC6). Excerpt from this description:
<<Right-click the block diagram to bring up the programming palette and go to Programming»Application Control and place the
    Invoke Node on the block diagram. Using the hand tool, click Method and select Library»Deploy Library>>
5) LabView BUG: Do NOT RUn the Application under the WIn XP SP2 Development Environment if the APP Deploys Shared Vars:
   This will cause the Dreaded TagSrv Error: "TagSrv.exe: This application has requested the runtime to terminate in an unusual way".
   After this Error has occured, it will reoccur each time WinXP SP2 is restarted, and (Network) Shared Variables will NOT work any more!
Geir Ove
Attachments:
LabView_Tagsrv_Error.jpg ‏26 KB

Hello Geir,
I have tried to reproduce the behavior you are seeing where .m file comments appear in the final built executable. However, I am unable to do so using LabVIEW 2009 SP1. I have a caller VI with a MathScript node that calls the adder function in adder.m. The contents of adder.m are as follows:
% ADDER This function adds 3 to its input variable
%   y = adder(x)
%   INPUT: x
%   OUTPUT: y, equal to x + 3
function y = adder(x)
y = x + 3;
I have configured the build specification as you mention in steps (1) and (2):
Additional Exclusions
- "Disconnect type definitions" Yes
- "Remove unused polymorphic VI instances" Yes
- "Remove unused members of project libraries" No
Advanced
- "Enable Debugging" No
At first, I did not include the adder.m file in the project. I built the application and was not able to find the text "adder" anywhere in the EXE. Then, I added the .m file to the project and put it in the "Always Included" section in "Source Files." Again, I was not able to find the search text in the built EXE. In step 3, you mention
geirove wrote:
   "Use LabView 8.x file layout": YES !!!!!!!
but in the 5th post in this thread, you state
geirove wrote:
Compile using the new compile method ( Use LabView 8.x file layout": NO),
I have tried both settings in the Advanced section, but again, I am not able to find any comments in the EXE. I even added a call to the "path" function in adder.m. This puts a warning glyph on the caller MathScript node and generates different code. The EXE will return an unknown symbol error for adder (any VI with a warning glyph will not work in a built app), but I am not able to find any comments in the EXE. This project is attached below.
As for your other item with a broken EXE if you call empty functions, I am unable to reproduce this as well. I have taken the last attachment to your third post in this thread (the log_write function) and called it from the caller VI as well. The EXE runs just fine and I do not find any comments in this EXE either.
Unfortunately, there was a rather serious issue in the LabVIEW 2009 MathScript RT Module, where some internal MathScript VIs could become corrupted when building executables. Have you tried running the "Find Bad Instantiations" tool from this Knowledge Base article? Simply installing the SP1 version on top may not have corrected any VIs that may be corrupted.
Due to our difficulty in reproducing the issues you mention, could you modify the attached project or else attach a new project, appropriately configured, that builds an EXE with .m comments embedded in it? This way, we can uncover any minute details that we're overlooking.
Grant M.
Senior Software Engineer | LabVIEW MathScript | National Instruments
Attachments:
MComments.zip ‏186 KB

Compilation problem with templates while using option -m64

Hi,
I have compilation problem with template while using option -m64.
No problem while using option -m32.
@ uname -a
SunOS snt5010 5.10 Generic_127111-11 sun4v sparc SUNW,SPARC-Enterprise-T5220
$ CC -V
CC: Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
Here is some C++ program
############# foo5.cpp #############
template <typename T, T N, unsigned long S = sizeof(T) * 8>
struct static_number_of_ones
static const T m_value = static_number_of_ones<T, N, S - 1>::m_value >> 1;
static const unsigned long m_count = static_number_of_ones<T, N, S - 1>::m_count + (static_number_of_ones<T, N, S - 1>::m_value & 0x1);
template <typename T, T N>
struct static_number_of_ones<T, N, 0>
static const T m_value = N;
static const unsigned long m_count = 0;
template <typename T, T N>
struct static_is_power_of_2
static const bool m_result = (static_number_of_ones<T,N>::m_count == 1);
template <unsigned long N>
struct static_number_is_power_of_2
static const bool m_result = (static_number_of_ones<unsigned long, N>::m_count == 1);
int main(int argc)
int ret = 0;
if (argc > 1)
ret += static_is_power_of_2<unsigned short, 16>::m_result;
ret += static_is_power_of_2<unsigned int, 16>::m_result;
ret += static_is_power_of_2<unsigned long, 16>::m_result;
ret += static_number_is_power_of_2<16>::m_result;
else
ret += static_is_power_of_2<unsigned short, 17>::m_result;
ret += static_is_power_of_2<unsigned int, 17>::m_result;
ret += static_is_power_of_2<unsigned long, 17>::m_result;
ret += static_number_is_power_of_2<17>::m_result;
return ret;
Compiation:
@ CC -m32 foo5.cpp
// No problem
@ CC -m64 foo5.cpp
"foo5.cpp", line 20: Error: An integer constant expression is required here.
"foo5.cpp", line 36: Where: While specializing "static_is_power_of_2<unsigned long, 16>".
"foo5.cpp", line 36: Where: Specialized in non-template code.
"foo5.cpp", line 26: Error: An integer constant expression is required here.
"foo5.cpp", line 37: Where: While specializing "static_number_is_power_of_2<16>".
"foo5.cpp", line 37: Where: Specialized in non-template code.
"foo5.cpp", line 20: Error: An integer constant expression is required here.
"foo5.cpp", line 43: Where: While specializing "static_is_power_of_2<unsigned long, 17>".
"foo5.cpp", line 43: Where: Specialized in non-template code.
"foo5.cpp", line 26: Error: An integer constant expression is required here.
"foo5.cpp", line 44: Where: While specializing "static_number_is_power_of_2<17>".
"foo5.cpp", line 44: Where: Specialized in non-template code.
4 Error(s) detected.
Predefined macro:
@ CC -m32 -xdumpmacros=defs foo5.cpp | & tee log32
@ CC -m64 -xdumpmacros=defs foo5.cpp | & tee log64
@ diff log32 log64
7c7
< #define __TIME__ "09:24:58"
#define __TIME__ "09:25:38"20c20
< #define __sparcv8plus 1
#define __sparcv9 1[snipped]
=========================
What is wrong?
Thanks,
Alex Vinokur

Bug 6749491 has been filed for this problem. It will be visible at [http://bugs.sun.com] in a day or two.
If you have a service contract with Sun, you can ask to have this bug's priority raised, and get a pre-release version of a compiler patch that fixes the problem.
Otherwise, you can check for new patches from time to time at
[http://developers.sun.com/sunstudio/downloads/patches/]
and see whether this bug is listed as fixed.

[solved] Cannot compile conky-cli (compiler cannot create executables)

I'm having what seems to be a pretty common problem, but I cannot solve it. I've searched google and the forums, and I'm sure the answer is very easy, but I'm just stuck.
==> Starting build()...
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: in `/tmp/yaourt-tmp-heleos/aur-conky-cli/conky-cli/src/conky-1.7.1.1':
configure: error: C compiler cannot create executables
See `config.log' for more details.
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed.
Aborting...
Error: Makepkg was unable to build conky-cli package.
If someone could point me in the right direction that would be great
Solved my own problem! Looks like it was a change I made to my makepkg.conf.... Does anyone have a CFLAGS that's safe for an i7?
Last edited by heleos (2009-08-25 01:07:24)

Do you (or someone else) have a pkgbuild that you would like to share? I'm in need of the ecj compiler, but didn't find a pkgbuild in aur (unlessed I missed it somehow)
Kind regards,
Simon

Removing compiler problem markers

Does anybody know why I keep getting a pop up window that is
telling me it can't find a marker id at some location number? I am
getting one of these messages about every other time I save and
compile and it is getting RATHER ANNOYING!!! What does it mean and
how do I eliminate it???
Thanks in advance for helping me lower my blood pressure!!!
Have an Ordinary Day...
KomputerMan ~|:-)

Yes, I am now getting the same error - but slightly different
wording
Removing compile problem markers (Time of error: blah blah
blah...)
The details section states:
An internal error occurred during "Removing compiler problem
markers".
java.lang.NullPointerException
I'm able to compile the same code with no problem from the
command line on a Linux box. Running the clean comand doesn't fix
this unfortunately.
Some background info: I'm running a FDS project against a
JBoss server on a windows XP machine.
So, I deleted my project and shut down flex builder. Then
removed the project files (.actionScriptProperties, .project, &
.flexProperties) and removed the project folder from the flex.war
folder in the jboss server. Restarted Flex Builder and created a
new project the same way the project was built. And wa-la the
problem is gone.
So, something has gone bad with the project, but I am not
sure what because a look a the previous project files and they all
seem normal. I was having problems with the project trying to
create the "Output Directory" early, but a rebuild of the project
seemed to fix that too.
hope this helps.
--Andy

J2ME - RMS - Record Enumeration - compilation problem

Hi,
Im trying to create RMS with Record Enumeration. Able to open a recordstore & write a record in it; while reading the record with record enumeration, im assigning the recordstore object to enumeration. Here compilation problem occurs. Im attaching the code which im working. Please help me to solve this issue.
import javax.microedition.midlet.*;
import javax.microedition.rms.*;
import javax.microedition.lcdui.*;
import java.io.*;
public class RecordEnumeration extends MIDlet implements CommandListener
     private Display display;
     private Alert alert;
     private Form form;
     private Command cmdOpen, cmdWrite, cmdRead, cmdClose, cmdDelete, cmdExit;
     private RecordStore rs = null;
     private RecordEnumeration re = null;
     public RecordEnumeration()
          display = Display.getDisplay(this);
          cmdOpen = new Command("Open", Command.SCREEN, 1);
          cmdWrite = new Command("Write", Command.SCREEN, 1);
          cmdRead = new Command("Read", Command.SCREEN, 1);
          cmdClose = new Command("Close", Command.SCREEN, 1);
          cmdDelete = new Command("Delete", Command.SCREEN, 1);
          cmdExit = new Command("Exit", Command.SCREEN, 1);
          form = new Form("RecordEnumeration");
          form.addCommand(cmdOpen);
          form.addCommand(cmdWrite);
          form.addCommand(cmdRead);
          form.addCommand(cmdClose);
          form.addCommand(cmdDelete);
          form.addCommand(cmdExit);
          form.setCommandListener(this);
     public void startApp()
          display.setCurrent(form);
     public void pauseApp()
     public void destroyApp(boolean unconditional)
     public void commandAction(Command cmd, Displayable displayable)
          if(cmd == cmdExit)
               destroyApp(true);
               notifyDestroyed();
          else if(cmd == cmdOpen)
               try
                    rs = RecordStore.openRecordStore("RecordEnumeration", true);
                    System.out.println("Opening Record");
               catch(Exception err)
                    alert = new Alert("Err Opening", err.toString(), null, AlertType.WARNING);
                    alert.setTimeout(Alert.FOREVER);
                    display.setCurrent(alert);
          else if(cmd == cmdWrite)
               try
                    String StringOutput[] = {"First Record", "Second Record", "Third Record"};
                    for (int x = 0; x < 3; x++)
                         byte[] byteOutputData = StringOutput[x].getBytes();
                         rs.addRecord(byteOutputData, 0, byteOutputData.length);
                         System.out.println("Record "+ x +" Added");
               catch (Exception err)
                    alert = new Alert("Err Writing", err.toString(), null, AlertType.WARNING);
                    alert.setTimeout(Alert.FOREVER);
                    display.setCurrent(alert);
          else if(cmd == cmdRead)
               try
                    StringBuffer buffer = new StringBuffer();
                    re = rs.enumerateRecords (null, null, false);
                    while (re.hasNextElement())
                         buffer.append(new String(re.nextRecord()));
                         buffer.append("\n");
                    alert = new Alert("Enumeration", buffer.toString(), null, AlertType.WARNING);
                    alert.setTimeout(Alert.FOREVER);
                    display.setCurrent(alert);
                    System.out.println("Reading");
               catch(Exception err)
                    alert = new Alert("Err Reading", err.toString(), null, AlertType.WARNING);
                    alert.setTimeout(Alert.FOREVER);
                    display.setCurrent(alert);
          else if(cmd == cmdClose)
               try
                    rs.closeRecordStore();
                    System.out.println("Closed");
               catch(Exception err)
                    alert = new Alert("Err Closing", err.toString(), null, AlertType.WARNING);
                    alert.setTimeout(Alert.FOREVER);
                    display.setCurrent(alert);
          else if(cmd == cmdDelete)
               try
                    RecordStore.deleteRecordStore("RecordEnumeration");
                    re.destroy();
                    System.out.println("Deleted");
               catch(Exception err)
                    alert = new Alert("Err Deleting", err.toString(), null, AlertType.WARNING);
                    alert.setTimeout(Alert.FOREVER);
                    display.setCurrent(alert);
These are the error which im getting while compiling in WTK.
C:\WTK2.5.1\apps\WritingMixedData\src\RecordEnumeration.java:60: incompatible types
found : javax.microedition.rms.RecordEnumeration
required: RecordEnumeration
                    RecordEnumeration re = rs.enumerateRecords(null,null,false);
                    ^
C:\WTK2.5.1\apps\WritingMixedData\src\RecordEnumeration.java:99: cannot find symbol
symbol : method hasNextElement()
location: class RecordEnumeration
                    while (re.hasNextElement())
                    ^
C:\WTK2.5.1\apps\WritingMixedData\src\RecordEnumeration.java:101: cannot find symbol
symbol : method nextRecord()
location: class RecordEnumeration
                         buffer.append(new String(re.nextRecord()));
                         ^
C:\WTK2.5.1\apps\WritingMixedData\src\RecordEnumeration.java:136: cannot find symbol
symbol : method destroy()
location: class RecordEnumeration
                    re.destroy();
                    ^
4 errors
Advices are welcome. Thanks in advance.
-Singu

Hi Guys,
J2ME TECHNOLOGIES
I created a record store and inserted record date "random" into it using the following code.
RecordStore rs = null;
try {
rs = RecordStore.openRecordStore( "myrs",true);
//rs = RecordStore.openRecordStore( "myrs",false );
rs.setMode(1,true);
ByteArrayOutputStream baos = new ByteArrayOutputStream();
DataOutputStream dos = new DataOutputStream(baos);
try{dos.writeUTF("random");}catch(Exception e){}
byte[] b = baos.toByteArray();
rs.addRecord(b, 0, b.length);
}catch(Exception e){}
I executed this MIDLET TO INSERT.
I closed the application and tried to look for the physical db file inside my application folder where i couldnt find it.
Then i tried to read the data from RECORD STORE myrs using the the same MIDlet by editing the aboe code as follows
RecordStore rs = null;
try {
rs = RecordStore.openRecordStore( "myrs",false);
byte[] recData = new byte[10];
ByteArrayInputStream bais = new ByteArrayInputStream(recData);
DataInputStream dis = new
DataInputStream(bais);
rs.getRecord(1, recData, 0);
try{System.out.println("UTF: " + dis.readUTF());}catch(Exception e){}
System.out.println("--------------------");
} catch( RecordStoreException e ){// couldn't open it or create it
System.out.println("data base creation error"+e);
But when i executed it the error occured
microedition.rms.RecordStoreNotFoundException: cannot find record store file
My question in my first code ive created the data store and inserted the values into my recordstore myrs
Then when i edit the code for creation into reading from the record store why the error occurs.Does the Midlet store the record store Temporarirly ONLY till the MIDLET LIFECYCLE.
IF SO what is the method and code to store the RECORD STORE PERMANENTLLY EVEN AFTER THE MIDLET EXECUTION QUITS.
///////////////////////kARTHEE

[Solved] dvbcut compile problems - New PKGBUILD fix!

Similar Messages

Maybe you are looking for