[Solved] Build Error compiling grub through abs

hi,
When I try to compile grub through abs, I get a build error almost straight away.
Here is the error message:
make[3]: Entering directory `/home/jonathan/abs/grub/src/grub_bios-2.00/grub-core/gnulib'
make[4]: Entering directory `/home/jonathan/abs/grub/src/grub_bios-2.00/grub-core/gnulib'
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../intl -MT argp-ba.o -MD -MP -MF .deps/argp-ba.Tpo -c -o argp-ba.o argp-ba.c
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../intl -MT argp-eexst.o -MD -MP -MF .deps/argp-eexst.Tpo -c -o argp-eexst.o argp-eexst.c
mv -f .deps/argp-ba.Tpo .deps/argp-ba.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../intl -MT argp-fmtstream.o -MD -MP -MF .deps/argp-fmtstream.Tpo -c -o argp-fmtstream.o argp-fmtstream.c
In file included from argp.h:22:0,
from argp-eexst.c:25:
./stdio.h:456:1: error: 'gets' undeclared here (not in a function)
make[4]: *** [argp-eexst.o] Error 1
make[4]: *** Waiting for unfinished jobs....
In file included from argp-fmtstream.h:27:0,
from argp-fmtstream.c:34:
./stdio.h:456:1: error: 'gets' undeclared here (not in a function)
make[4]: *** [argp-fmtstream.o] Error 1
make[4]: Leaving directory `/home/jonathan/abs/grub/src/grub_bios-2.00/grub-core/gnulib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/jonathan/abs/grub/src/grub_bios-2.00/grub-core/gnulib'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/jonathan/abs/grub/src/grub_bios-2.00/grub-core/gnulib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jonathan/abs/grub/src/grub_bios-2.00'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Any help on how to fix the error will be appreciated.
Last edited by rabbidrabbit (2012-07-22 17:04:37)

https://lists.gnu.org/archive/html/grub … 00051.html

Similar Messages

Cannot compile gcc through abs

I seem to have problems compiling gcc through abs. It chugs away for a while, compiling, and after a while when reaching a second configuration part (?), it fails. This is the last piece of the output:
creating cache ../config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for gawk... gawk
checking whether ln -s works... yes
checking for gcc... /var/abs/base/gcc/src/gcc-3.3.6/gcc/xgcc -B/var/abs/base/gcc/src/gcc-3.3.6/gcc/ -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
checking whether we are using GNU C... yes
checking whether /var/abs/base/gcc/src/gcc-3.3.6/gcc/xgcc -B/var/abs/base/gcc/src/gcc-3.3.6/gcc/ -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include accepts -g... yes
checking for c++... /var/abs/base/gcc/src/gcc-3.3.6/gcc/xgcc -shared-libgcc -B/var/abs/base/gcc/src/gcc-3.3.6/gcc/ -nostdinc++ -L/var/abs/base/gcc/src/gcc-3.3.6/i686-pc-linux-gnu/libstdc++-v3/src -L/var/abs/base/gcc/src/gcc-3.3.6/i686-pc-linux-gnu/libstdc++-v3/src/.libs -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
checking whether we are using GNU C++... yes
checking whether /var/abs/base/gcc/src/gcc-3.3.6/gcc/xgcc -shared-libgcc -B/var/abs/base/gcc/src/gcc-3.3.6/gcc/ -nostdinc++ -L/var/abs/base/gcc/src/gcc-3.3.6/i686-pc-linux-gnu/libstdc++-v3/src -L/var/abs/base/gcc/src/gcc-3.3.6/i686-pc-linux-gnu/libstdc++-v3/src/.libs -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include accepts -g... yes
checking for GCC version number... 3.3.6
checking for strerror in -lcposix... no
checking for as... as
checking for ar... ar
checking for ranlib... ranlib
checking for a BSD compatible install... /bin/install -c
checking whether to enable maintainer-specific portions of Makefiles... no
CPU config directory is cpu/i486
OS config directory is os/gnu-linux
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking for ld used by GCC... ld
checking if the linker (ld) is GNU ld... yes
checking for ld option to reload object files... -r
checking for BSD-compatible nm... nm
checking how to recognise dependant libraries... pass_all
checking for object suffix... configure: error: installation or configuration problem; compiler does not work
make: *** [configure-target-libstdc++-v3] Error 1
==> ERROR: Build Failed. Aborting...
Any ideas why this might be?

due to a recent upgrade of freetype it now needs to be included differently in the source files.
I think you can solve the problem by editing mozilla/gfx/src/gtk/nsDeviceContextGTK.cpp
and adding
#include <ft2build.h>
#include FT_FREETYPE_H
somewhere at the top of the file where other lines starting with #include are
you may have do do this with other files as well, if you get this error again.
if you run makepkg again, all changes you made are undone, so it would be easier if someone could make a patch file

One Solve for "Error Compiling movie" Unknown Error

Just went through a hair-pulling hour trying to figure out why a sequence that had rendered in the past was suddenly not rendering anymore. The footage is HD DSLR footage at 1080p, with a separate audio track. Simple cuts and effects, and an adjustment layer for color-correction.
I had just successfully compiled another clip in the project and the only difference I could see was that at some point I had added a cross disolve from a Title clip to the Adjustment layer that was in the same (Video 2) track. Not sure why I did this, but it must have gotten dropped down from track 3.
I removed that cross disolve by moving the Adjustment layer to a new Video track, and fixing the Title's fade out. Sure enough, it works!
It's a stupid error, but if you find yourself in the same situation, hopefully this could help.
Stephen

Glad that you found a "cure," and for others, who might receive the error, for other reasons, this Adobe KB Article might be useful: http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-rendering-or.html
Good luck, and thanks for reporting.
Hunt

Flash Builder Error Compiling Ipad Actionscript Mobile Project.

I just bought a brand new ipad for testing. I am using flash buider 4.7 to make an actionscript mobile project. I created an app ID, provisioning profile, and certificate. I have done this before in flash professional so it wasn't too bad. However, when I run or debug even a blank application I get this error in flash builder:
Error occurred while packaging the application:
'Launching AppName' has encountered a problem.
Error occurred while packaging the application.
Exception in thread "main" java.lang.Error: Unable to find llvm JNI lib in:
/Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK/lib/adt.jar/Darwin
/Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK/lib/aot/lib/x64
/Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK/lib/adt.jar
/Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK/lib
                at adobe.abc.LLVMEmitter.loadJNI(LLVMEmitter.java:582)
                at adobe.abc.LLVMEmitter.<clinit>(LLVMEmitter.java:596)
                at com.adobe.air.ipa.AOTCompiler.generateExtensionsGlue(AOTCompiler.java:419)
                at com.adobe.air.ipa.AOTCompiler.generateMachineBinaries(AOTCompiler.java:1790)
                at com.adobe.air.ipa.IPAOutputStream.createIosBinary(IPAOutputStream.java:378)
                at com.adobe.air.ipa.IPAOutputStream.finalizeSig(IPAOutputStream.java:762)
                at com.adobe.air.ApplicationPackager.createPackage(ApplicationPackager.java:91)
                at com.adobe.air.ipa.IPAPackager.createPackage(IPAPackager.java:245)
                at com.adobe.air.ADT.parseArgsAndGo(ADT.java:571)
                at com.adobe.air.ADT.run(ADT.java:419)
                at com.adobe.air.ADT.main(ADT.java:469)
I have no idea where to even start in trying to figure out what could be the problem. I am pretty sure the itunes developer information is correct. Are there any kinds of drivers or developer modes that I need to set for a new iPad?
Thanks!

Thanks Shongrunden for your reply.
Yes, you are right. If I make a new Flex mobile project, I did not see the issue.
But that did not fully answer my question, my concern is: can an actionscript project use spark components?
Thanks.

[Solved]Error compiling kernel from abs

Hello Everyone,
I've hit a wall trying to compile the kernel from the abs. I get this error message:
patching file fs/fat/inode.c
Hunk #1 succeeded at 800 (offset 74 lines).
HOSTCC scripts/basic/fixdep
/bin/sh: scripts/basic/fixdep: cannot execute binary file
make[2]: *** [scripts/basic/fixdep] Error 126
make[1]: *** [scripts_basic] Error 2
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_32.h
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_64.h
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
make: *** Waiting for unfinished jobs....
HOSTCC scripts/basic/fixdep
SYSHDR arch/x86/syscalls/../include/generated/asm/unistd_x32.h
SYSTBL arch/x86/syscalls/../include/generated/asm/syscalls_32.h
/bin/sh: scripts/basic/fixdep: cannot execute binary file
make[1]: *** [scripts/basic/fixdep] Error 126
make: *** [scripts_basic] Error 2
==> ERROR: A failure occurred in build().
Aborting...
While trying to figure this out I came across this post: https://bbs.archlinux.org/viewtopic.php?id=99089 and have tried the solutions presented. I did end up having to change my fstab to include defaults,
/dev/sda3 /home ext4 defaults,exec,rw,relatime,data=ordered 0 2
and the permissions on scripts/basic/fixdep are: -rwxr-xr-x which i think it correct.
Unfortunately, the problem still exists and I don't know how to continue trouble shooting. Can someone point me in a direction to troubleshoot this?
Last edited by magyarm (2012-12-20 01:55:00)

magyarm wrote:So now, I need to figure out a good way to handle multiple compilers on my system to prevent this from happening again. If anyone has any tips I would love to hear them.
Set up a file that you source from bash to prepend the cross compiler to your path, that would only be active for that shell, and when you're done just close it. Means you only activate the cross compiler when you need it.

Build error importing MyFaces 1.0.7

Hi,
I'm trying to use the MyFaces components in SJSC, but when I import myfaces-components.jar into JSCS I get the following build-error:
compile-beaninfo:
Compiling 35 source files to C:\Documents and Settings\Iwan\.Creator\1_0\components\jars\beaninfo-classes
C:\Documents and Settings\Iwan\.Creator\1_0\components\jars\beaninfo-src\net\sourceforge\myfaces\component\html\ext\HtmlCommandButtonBeanInfo.java:99: exception java.beans.IntrospectionException is never thrown in body of corresponding try statement
} catch (IntrospectionException e) {
^
1 error
startup\bin\create-dt-jar.xml [71] Compile failed; see the compiler error output for details.
BUILD FAILED (total time: 50 seconds)I have no clue as to what is going on, and since there seem to be no official announcement of SUN to add more sophisticated components to Creator, I guess we're stuck with the ones we get.
Iwan

I found a way to import that library so you can use the MyFaces components by dragging and dropping. It is a little bit of a hack, but it works.
Steps to add library:
1. You need to try to import the component jar first. This importing will create the .Creator\1_0\components\jars directory in the user home (i.e. C:\Documents and Settings\<YOUR USERNAME>\.Creator\1_0\components\jars).
2. Download and install WildEdit.
3. Run WildEdit and point it at .Creator\1_0\components\jars\beaninfo-src directory. (i.e. C:\Documents and Settings\<YOUR USERNAME>\.Creator\1_0\components\jars\beaninfo-src)
4. In the replace textbox of WildEdit type "IntrospectionException " (no quotes but 1 space at the end or could do a regular expression with whitespace at the end)
5. In the Replace With textbox of WildEdit type "Exception " (no quotes but 1 space at the end).
6. In Files matching, type *.java.
7. In Character Encoding, UTF-8.
8. Check Search Subfolders.
9. Try importing the jar again.
10. During import run the Replace All utility of WildEdit against the directory continuously (i.e. click the green arrow a bunch of times) until you see repeatedly in the Log tab at bottom of WildEdit:
Number of files searched: 35
Number of files modified: 0
Total changes made: 0
These steps added the components in my Creator application, but only the components seem to have been added. The validators will have to be added by hand, but that is not too hard via the page source.
Regards,
Marc

[SOLVED] [mkinitcpio] initramfs "build error" messages since v.18-1

Hi everybody,
Since the update from mkinitcpio 17-1 to 18-1 I get those build error messages while running mkinitcpio:
# mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.15.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.15.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
-> Running build hook: [lvm2]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
However I can still boot and everything seems mostly fine. I haven't changed anything to my /etc/mkinitcpio.conf, here are the only customized parts:
MODULES="i915 dm_snapshot"
HOOKS="base udev autodetect modconf block keymap encrypt lvm2 filesystems keyboard fsck
I'm using an encrypted root (ext4 over LVM over LUKS) and boot partition is contained in an (unencrypted) LVM logical volume. I also specify a few i915 module options in an /etc/modprobe.d/modprobe.conf file as per the Intel Graphics wiki page:
# Intel graphics driver power-saving option :
options i915 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
Never had any such warnings before, but now it appears each and every time I update or reinstall my kernel (the default one). I went through Mkinitcpio wiki page, tried putting question marks after the listed modules and rebuilding but it didn't change anything... Any ideas?
Btw, I don't use any specific compression option and had the regular lzo name change during the same full system upgrade that updated mkinitcpio and linux.
Thanks
Last edited by Neitsab (2014-08-04 11:51:19)

Yes indeed, removing /etc/modprobe.d/modprobe.conf~ hidden backup file solved the warning issue. Strange but thanks ukhippo, I hadn't thought about checking other subforums!
Last edited by Neitsab (2014-08-04 11:52:08)

How do I solve 'error compiling movie. unknown error'?

how do I solve 'error compiling movie. unknown error' when trying to export? I think a file is damaged or conflicting but how do I know which one?
Also, how did this happen in the first place and how can I avoid it in the future?
Thank you very much!!

BSHF
The answers are in the details which are lacking in your report.
What version of Premiere Elements are you using and on what computer operating system is it running?
Please check out the Adobe troubleshooting documents for this issue
Error "Error compiling movie" during render or export
Troubleshoot damaged projects | Adobe Premiere Elements
After you review those documents and determine if either suggested troubleshooting scheme will work for you,
then we can discuss the immediate and future actions.
Looking forward to your follow up. Depending on your reply, next posts may require of you details
a. project settings
b. properties of your source media
c. edits and inspection of Timeline content with the Timeline expanded with the -+ slider above the Timeline.
More later.
ATR

Another Compiler Bug (message: An internal build error has occurred... Unknown Flex Problem)

I was fighting with this problem for a few days. Finally I've got it resolved. I want to describe it and fill in BUG in the bug report, but I am not sure about Adobe support options. So, I am putting bug report here.
1. ASSUMPTION: All problems which compiler reports as unknown problem are the real compiler BUGs/Problems. Eventually MXML compiler/ActionScript compiler should be able to take C++ or FORTRAN code or an aribitrary text and nicely tell "Error: It is not ActionScript (Flex) code" or "the code is corrupted from Line so and so...". When compiler crashed, it is most probably due to one of the states not handled (or not handled correct). Keeping this in mind I assume, that my code has nothing to do with the compiler crash.
2. PROBLEM Description.
     - I tried to port our internal project from Flex3.5/Flex Builder 3 to Flex4.1/Flash Builder 4.
     - After checking out and trying to build code I start getting weird problems like Error 1037: Packages cannot be nested.
     - After cleaning and compiling project by project, walking up dependency tree, I was able to get rid of this problem.
     - On last Project I've got another problem (An internal build error has occurred... Unknown Flex Problem). Which I stuck with for a while.
     - When I checked log file I found following messages:
============================================================
!ENTRY com.adobe.flexbuilder.project 4 43 2010-12-21 15:45:24.353
!MESSAGE Uncaught exception in compiler
!STACK 0
java.lang.ClassCastException: macromedia.asc.parser.InputBuffer cannot be cast to flex2.compiler.as3.CodeFragmentsInputBuffer
at flex2.compiler.as3.AbstractSyntaxTreeUtil.lineNumberToPosition(AbstractSyntaxTreeUtil.jav a:1266)
at flex2.compiler.mxml.ImplementationGenerator.generateBinding(ImplementationGenerator.java: 569)
at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetupFunction(ImplementationG enerator.java:863)
at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetup(ImplementationGenerator .java:812)
at flex2.compiler.mxml.ImplementationGenerator.generateInitializerSupportDefs(Implementation Generator.java:1878)
at flex2.compiler.mxml.ImplementationGenerator.generateClassDefinition(ImplementationGenerat or.java:1044)
at flex2.compiler.mxml.ImplementationGenerator.<init>(ImplementationGenerator.java:206)
at flex2.compiler.mxml.ImplementationCompiler.generateImplementationAST(ImplementationCompil er.java:499)
at flex2.compiler.mxml.ImplementationCompiler.parse1(ImplementationCompiler.java:197)
at flex2.compiler.mxml.MxmlCompiler.parse1(MxmlCompiler.java:168)
at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2871)
at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2824)
at flex2.compiler.CompilerAPI.batch2(CompilerAPI.java:446)
at flex2.compiler.CompilerAPI.batch(CompilerAPI.java:1274)
at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1496)
at flex2.tools.oem.Application.compile(Application.java:1188)
at flex2.tools.oem.Application.recompile(Application.java:1133)
at flex2.tools.oem.Application.compile(Application.java:819)
at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:344)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(A SApplicationBuilder.java:276)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplication Builder.java:127)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:190)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:7 4)
at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectB uilder.java:480)
at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuild er.java:306)
at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncremen talBuilder.java:157)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516)
at org.eclipse.core.internal.resources.Project.build(Project.java:94)
at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:221)
at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162)
at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38 )
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SESSION 2010-12-22 09:48:27.766 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -data C:\Client_Flex4 -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
================================================
3. RESOLUTION/WORK AROUND
     - I was able to get this problem cleared by putting compiler option for Flex Application projects: -keep-generated-actionscript
4. SIDE NOTE
I do not really see putting this compiler option as the solution and living with the mistery is making me fill a bit bad.

Hi Faser,
I just tried it on Vista with our latest FB Plugin build but
I was unable to reproduce your issue with the following setup:
- FB Plugin build installed by Administrator account user
under her Documents folder
- Administrator account user can launch, create Flex projects
under her own workspace without any problems
- Standard account user can launch the FB Plugin build (need
Admin's password) and create Flex project (default location) under
his own workspace
If your setup is different, can you please log a bug at
http://bugs.adobe.com/flex.
Be sure to include what build you are using, whether it's
reproducible, the detail of the setup, etc...
thanks,
Sharon

Error compiling deluge [solved]

So I downloaded the most recent pkgbuild of deluge (0.9.04) and used makepkg -sp
Unfortunately I receive the following error after a bit of compiling takes place:
/usr/bin/ld: cannot find -lboost_thread
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1
install: cannot stat `pixmaps/deluge.svg': No such file or directory
==> ERROR: Build Failed.
Aborting...
I know I have all the dependencies installed, so I'm not sure what is going wrong here.
Any thoughts are appreciated!
Edit: I found the svn version in the AUR that has fixed the boost build error.
http://aur.archlinux.org/packages.php?ID=18502
Last edited by nycthbris (2008-08-04 21:00:22)

Here is the patch.
boost-mt.patch:
*** ./setup_old.py 2008-08-21 12:36:56.000000000 +0200
--- ./setup.py 2008-08-21 12:39:51.000000000 +0200
*** 157,167 ****
else:
_include_dirs += ['/usr/include/python' + python_version]
_libraries = [
! 'boost_filesystem',
! 'boost_date_time',
! 'boost_iostreams',
! 'boost_python',
! 'boost_thread',
'pthread',
'ssl',
'z'
--- 157,167 ----
else:
_include_dirs += ['/usr/include/python' + python_version]
_libraries = [
! 'boost_filesystem-mt',
! 'boost_date_time-mt',
! 'boost_iostreams-mt',
! 'boost_python-mt',
! 'boost_thread-mt',
'pthread',
'ssl',
'z'
And here is the PKGBUILD:
pkgname=deluge
pkgver=0.9.07
pkgrel=1
pkgdesc="A bittorrent client written with python and pygtk"
arch=('i686' 'x86_64')
url="http://deluge-torrent.org/"
license=('GPL2')
depends=('pygtk' 'boost' 'pyxdg' 'dbus-python' 'librsvg' 'setuptools')
makedepends=('subversion' 'intltool')
conflicts=('deluge')
provides=('deluge')
source=(http://download.deluge-torrent.org/source/$pkgver/$pkgname-$pkgver.tar.gz boost-mt.patch)
md5sums=('d5e73b6d997040a70ecf948950cf4a51'
'7cafc0c498383545ed45436f3c007a24')
options=('!emptydirs')
build() {
cd $startdir/src/$pkgname-$pkgver
patch -Np1 -i ${srcdir}/boost-mt.patch || return 1
python setup.py install --prefix=/usr --root=$startdir/pkg
install -D -m644 deluge/data/pixmaps/deluge.svg $startdir/pkg/usr/share/pixmaps/deluge.svg
Or get complete tarball → http://fisiu.lua.pl/arch/tarball/deluge.tar.bz2

How to solve this Folio Builder error :

We have uploaded 18 magazine titles on DPS for the month of December and for some reason magazine with large file size cannot be accessed.
Can you provide information on how to solve this error:
" Folio Builder error: An error has occured while loading your documents from the server. Network failure."
thanks,

Have a look at these docs:
E-CA Change Assistant gives error: All agents should be running and sending pulses for all application, batch, file and web servers for the environment before the Change Assistant is started (Doc ID 1073464.1)
E-CA: PT8.53, PT8.52, PT8.51, PT8.50: EMF Agents not Finding Configuration Files for App Server, Batch Server (Doc ID 1080590.1)

Release build error with ANE "AOT Compilation has failed while optimizing function"

I'm trying to use the ChartBoost ANE which can be downloaded here https://github.com/freshplanet/ANE-Chartboost
When I do an Ad-hoc release build It keeps crashing and giving me the error below when packaging for iOS. But if I do a debug build that's a "fast" or "standard" build it compiles fine, and I can even see the ads.
Why would it crash when doing a release build? Does this ANE need an update?
I'm using FB 4.7 and AIR 3.8. Specifically, Apache Flex 4.10 Air 3.8
If I remove this 1 line of the Chartboost ANE code "AirChartboost.getInstance().showInterstitial();", the release build compiles fine and I can put it on the test iOS device.
"Error occurred while packaging the application:
AOT Compilation has failed while optimizing function public::AdsHelper.showFullscreenAd
Exception in thread "main" java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.containsKey(TreeMap.java:209)
at adobe.abc.GlobalOptimizer.sccp_eval(GlobalOptimizer.java:6150)
at adobe.abc.GlobalOptimizer.sccp_analyze(GlobalOptimizer.java:6019)
at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4733)
at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3615)
at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2309)
at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:534)
at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:343)
at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:611)
at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:104)
Compilation failed while executing : ADT"

I just encountered this error when building ad-hoc package, say that:
Error occurred while packaging the application:
AOT Compilation has failed while optimizing function apackage::AClass.aFunction
After several tries It turns out that the error was because the function aFunction has a return before some other code (for testing). I commented the code after the return then the packaging works fine.
FYI.

[SOLVED] Xsane Build Errors

xsane: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
Prompted me to rebuild sane-backends-1.0.20 against libjpeg 7-1 (no problems there) and xsane (with build errors):
--disable-gimp --disable-nls --disable-sanetest --disable-gimptest --disable-gtktest --prefix=/usr/local
xsane-back-gtk.c: In function 'xsane_back_gtk_range_display_value_right_callback':
xsane-back-gtk.c:1966: warning: cast from pointer to integer of different size
xsane-back-gtk.c: In function 'xsane_back_gtk_range_new':
xsane-back-gtk.c:2016: warning: cast to pointer from integer of different size
xsane-back-gtk.c: In function 'xsane_back_gtk_set_sensitivity':
xsane-back-gtk.c:2615: error: 'SANE_CAP_ALWAYS_SETTABLE' undeclared (first use in this function)
xsane-back-gtk.c:2615: error: (Each undeclared identifier is reported only once
xsane-back-gtk.c:2615: error: for each function it appears in.)
make[1]: *** [xsane-back-gtk.o] Error 1
Is there a known resolution/workaround for this?
Last edited by adamlau (2009-07-15 18:38:39)

Just noticed the MissingCapsFlag.patch, build went without a hitch, xsane works as expected...
Last edited by adamlau (2009-07-15 19:18:39)

One cause for "Error Compiling Movie: Unknown Error"

I just finished a huge promotional video project, one which was fraught with problems.
To start out with, most of my interview footage was RED Epic material, and my b-roll was comprised of a combination of RED Epic (some at 4kHD and some at 5k), RED ONE (some at 4k, some at 3k), XDCAM-EX 1080p, HDV 1080i, Sony AVCHD 1080p, previously exported Vimeo HD h.264 material, and still shots. Needless to say, quite a mess of codecs and odd file types to combine into one project.
Since much of my b-roll was 1080p, I decided to do my entire edit on a 1080p timeline; however, since all my interview footage was RED, I decided to use a RED Epic 1080p timeline. In doing so, I discovered something important about Premiere, and I don't know if this is a bug, or if it's meant to work this way: when you put 5k RED Epic material on a 1080p timeline and use the zoom controls in the motion effects panel to bring it to size, and attempt to export, you'll get the "Error Compiling Movie: Unknown Error" every time. This may happen with other types of footage that's too big for the timeline too, i'm not sure. However, when you instead right click on the clip and use the "scale to frame size" command, it exports just fine, with no errors.
I also discovered that (at least with my setup), PrPro can't handle large stills on the timeline; I contiually got OpenGL crash errors until I resized all my images in Photoshop to be no more than 1920px wide.
The promo video is 11:30, and comprised of five segments. I edited each segment (interview and b-roll) in it's own sequence, and then nested the sequences along with the transition/motion graphics/title slides between them on my master sequence. However, I kept getting crashes and freezes when attempting to export that master sequence which I couldn't explain. Ultimately I had to export each of the individual sequences as a Lagarith UT AVI file, and then import that file back in and place it in the master sequence where the nested sequence had been. Once that was done it exported fine, so I'm still not sure what the problems were, since each individaul sequence exported okay, and the master exported just fine after replacing the nested sequences with the Lagarith clips...
Anyway, I think I've got a pretty good promo done, and it's definitely a TON better than our last one. When I get it online I'll post a link over in the Lounge and ask for feedback...

So, I ran into this the first time recently. I discovered it when I copied an adjustment layer for quick grading with an RGB Color Corrector and Color Balance effects in it from a rehearsal cut of a short film.The effects worked fine and rendered out without issue. I imported the sequence into my 'final' cut so I could reuse the titles and adjustment layer. I copied the adjustment layer to the new rough cut of the final sequence and ran into this error when I tried to render it, but only after applying the adjustment layer. I found that if I turned off the Color Balance, the sequence rendered fine. I found that if I moved the Color Balance above the RGB Color Corrector, the effect of the RGB effect completely disappeared AND it rendered correctly (both effects turned on) - so reversing the order worked, but effects were weird. I also found that if I added ANY non-GPU accelerated effects to the RGB Color Corrector that I'd get the same compile error (unknown).
I went through and deleted clips until I got to 0 on the timeline, added a new one back on, and it still wouldn't render. So, I created an entirely NEW sequence, copied all video and audio (not adjustment layer) from the original failing rough cut of the final sequence, and pasted it into this new sequence. I also copied the adjustment layer again from the rehearsal cut into this new sequence and it is rendering just fine.
HOURS WASTED DOING THIS! It would be awesome if Adobe actually tested their products before releasing them instead of forcing us to do it for them. My project consisted of about 30-40 different clips and audio, all from the same DSLR (Nikon D810), nothing fancy, two effects in an adjustment layer applied to the entire sequence, and Premiere couldn't handle it. Given this and some of the comments I read while troubleshooting this on this forum, gives me pause in trusting Adobe products for any real work that has a deadline (unless, of course, you build in the required Adobe testing time into your budget).
So, just another data point; something else to try. Create a new sequence, and copy everything from your non-working one to it, and see if this will jump-start Premier. Worked for me. Good luck.

Unknown error compiling movie - tiny sections export fine - no one bad clip

This week I've been dealing with a huge pain exporting a 6 minute video on my retina macbook pro. The sequence is 720p 24fps (23.976) and contains a mix of 720p & 1080p (scaled) AVCHD footage, a couple of 1080p GoPro shots, some 1080p time-lapse clips (quicktime h.264) and some mp3 files.
Earlier I was having trouble with playback in premiere, but by replacing one bad clip and rendering the rest in small chunks I am now able to play back the sequence with zero issues within premiere.
However, when I go to export the whole movie, or even a significant chunk, either the system starts spinning its wheels partway through export or I get "error compiling movie - unknown error."
The workaround I have found when that happens is to restart premiere (often having to force quit) and then try to export a smaller chunk. (Restarting seems to be necessary after an export has failed). Sometimes the chunks become ridiculously small, but there is no one clip or section that won't export if the clips are small enough. I have also tried cleaning the media cache trashing the preferences, neither of which have changed anything.
Even when I export using the sequence settings of the sequence (which has already been rendered and plays fine within premiere) the problem persists.
My first question is: how can there be an issue exporting a video with identical settings to a sequence that has already been rendered and plays back fine?? Am I wrong in understanding that no conversion is required in that case? Clearly there is something about the process that I don't understand.
My second question is, if no one clip or clips are to blame, are there any likely culprits in my system? Is there perhaps a less time-consuming workaround?
Finally I want to ask: what good does it do to allow users to put different types of media into one timeline if they can never export it?!?!
This is super frustrating, thank you for any help or insight.

So, I ran into this the first time recently. I discovered it when I copied an adjustment layer for quick grading with an RGB Color Corrector and Color Balance effects in it from a rehearsal cut of a short film.The effects worked fine and rendered out without issue. I imported the sequence into my 'final' cut so I could reuse the titles and adjustment layer. I copied the adjustment layer to the new rough cut of the final sequence and ran into this error when I tried to render it, but only after applying the adjustment layer. I found that if I turned off the Color Balance, the sequence rendered fine. I found that if I moved the Color Balance above the RGB Color Corrector, the effect of the RGB effect completely disappeared AND it rendered correctly (both effects turned on) - so reversing the order worked, but effects were weird. I also found that if I added ANY non-GPU accelerated effects to the RGB Color Corrector that I'd get the same compile error (unknown).
I went through and deleted clips until I got to 0 on the timeline, added a new one back on, and it still wouldn't render. So, I created an entirely NEW sequence, copied all video and audio (not adjustment layer) from the original failing rough cut of the final sequence, and pasted it into this new sequence. I also copied the adjustment layer again from the rehearsal cut into this new sequence and it is rendering just fine.
HOURS WASTED DOING THIS! It would be awesome if Adobe actually tested their products before releasing them instead of forcing us to do it for them. My project consisted of about 30-40 different clips and audio, all from the same DSLR (Nikon D810), nothing fancy, two effects in an adjustment layer applied to the entire sequence, and Premiere couldn't handle it. Given this and some of the comments I read while troubleshooting this on this forum, gives me pause in trusting Adobe products for any real work that has a deadline (unless, of course, you build in the required Adobe testing time into your budget).
So, just another data point; something else to try. Create a new sequence, and copy everything from your non-working one to it, and see if this will jump-start Premier. Worked for me. Good luck.

[Solved] Build Error compiling grub through abs

Similar Messages

Maybe you are looking for