Maybe solved pacman : could not open package: File too large

please help! i just made a PKGBUILD for Unreal Tournament 2004 (spent a lot of time on it!) now it says it can't install it. the finished file is 2.6gb. what to do? thanks much.. i want to upload it to AUR.
thanks
karsten

Sigi wrote:I think he wrote a PKGBUILD to install the DVD content in an "Arch friendly" way. (With the background that the linux installer apparently isn't available on every edition of the UT2k4 DVD)
exactly.. its reads the files and installs it according to Arch. how do i get pacman to not die?? thanks..

Similar Messages

[SOLVED] Pacman - could not open file

After being forced to downgrade my firmware in this thread I get the following error in pacman...
:: Starting full system upgrade...
resolving dependencies...
[b]error: could not open file /var/lib/pacman/local/linux-firmware-20120227-2/desc: No such file or directory[/b]
looking for inter-conflicts...
Any idea how I stop this?
Last edited by Swarfega (2012-05-17 09:03:10)

Yeah thanks. Just done that and get the following
[root@xv5-ln01 andrewp]# pacman -S linux-firmware
warning: linux-firmware-20120227-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
error: could not open file /var/lib/pacman/local/linux-firmware-20120227-2/desc: No such file or directory
Targets (1): linux-firmware-20120227-2
Total Installed Size: 38.73 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [###########################################################################] 100%
(1/1) loading package files [###########################################################################] 100%
(1/1) checking for file conflicts [###########################################################################] 100%
error: failed to commit transaction (conflicting files)
linux-firmware: /usr/lib/firmware/GPL-3 exists in filesystem
linux-firmware: /usr/lib/firmware/TDA7706_OM_v2.5.1_boot.txt exists in filesystem
linux-firmware: /usr/lib/firmware/TDA7706_OM_v3.0.2_boot.txt exists in filesystem
linux-firmware: /usr/lib/firmware/agere_ap_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/agere_sta_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ar7010.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar7010_1_1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar9170-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar9170-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ar9271.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ath3k-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/atmsar11.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1-4.8.53.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1-5.2.13.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1-5.2.7.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1h-4.8.53.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1h-5.2.13.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/bnx2x-e1h-5.2.7.0.fw exists in filesystem
linux-firmware: /usr/lib/firmware/dvb-fe-xc5000-1.6.114.fw exists in filesystem
linux-firmware: /usr/lib/firmware/dvb-usb-dib0700-1.20.fw exists in filesystem
linux-firmware: /usr/lib/firmware/dvb-usb-terratec-h5-drxk.fw exists in filesystem
linux-firmware: /usr/lib/firmware/emi62/bitstream.fw exists in filesystem
linux-firmware: /usr/lib/firmware/emi62/loader.fw exists in filesystem
linux-firmware: /usr/lib/firmware/emi62/midi.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/ms_init.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/ms_rdwr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/msp_rdwr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/sd_init1.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/sd_init2.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ene-ub6250/sd_rdwr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ess/maestro3_assp_kernel.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ess/maestro3_assp_minisrc.fw exists in filesystem
linux-firmware: /usr/lib/firmware/f2255usb.bin exists in filesystem
linux-firmware: /usr/lib/firmware/htc_7010.fw exists in filesystem
linux-firmware: /usr/lib/firmware/htc_9271.fw exists in filesystem
linux-firmware: /usr/lib/firmware/i2400m-fw-usb-1.4.sbcf exists in filesystem
linux-firmware: /usr/lib/firmware/i2400m-fw-usb-1.5.sbcf exists in filesystem
linux-firmware: /usr/lib/firmware/i6050-fw-usb-1.5.sbcf exists in filesystem
linux-firmware: /usr/lib/firmware/intelliport2.bin exists in filesystem
linux-firmware: /usr/lib/firmware/isci/Makefile exists in filesystem
linux-firmware: /usr/lib/firmware/isci/README exists in filesystem
linux-firmware: /usr/lib/firmware/isci/create_fw.c exists in filesystem
linux-firmware: /usr/lib/firmware/isci/create_fw.h exists in filesystem
linux-firmware: /usr/lib/firmware/isci/isci_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/isci/probe_roms.h exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-100-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-1000-3.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-1000-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-105-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-135-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-2000-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-2030-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-3945-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-4965-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5000-1.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5000-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5000-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-5150-2.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000-4.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000g2a-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000g2b-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6000g2b-6.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6050-4.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/iwlwifi-6050-5.ucode exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/new_code.bin exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/new_code_fix.bin exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/trigger_code.bin exists in filesystem
linux-firmware: /usr/lib/firmware/kaweth/trigger_code_fix.bin exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/mpr.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa18x.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19qi.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19qw.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa19w.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28x.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28xa.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa28xb.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa49w.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan/usa49wlc.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/Makefile exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/keyspan_pda.S exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/keyspan_pda.fw exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/xircom_pgs.S exists in filesystem
linux-firmware: /usr/lib/firmware/keyspan_pda/xircom_pgs.fw exists in filesystem
linux-firmware: /usr/lib/firmware/korg/k1212.dsp exists in filesystem
linux-firmware: /usr/lib/firmware/lbtf_usb.bin exists in filesystem
linux-firmware: /usr/lib/firmware/lgs8g75.fw exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8381.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8381_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8385.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/cf8385_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8682.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8682_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8686_v9.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8686_v9_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8688.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/gspi8688_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/lbtf_sdio.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8385.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8385_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8682.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8682_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v8.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v8_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v9.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8686_v9_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8688.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/sd8688_helper.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8388_olpc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8388_v5.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8388_v9.bin exists in filesystem
linux-firmware: /usr/lib/firmware/libertas/usb8682.bin exists in filesystem
linux-firmware: /usr/lib/firmware/matrox/g200_warp.fw exists in filesystem
linux-firmware: /usr/lib/firmware/matrox/g400_warp.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mrvl/sd8787_uapsta.bin exists in filesystem
linux-firmware: /usr/lib/firmware/mts_cdma.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_edge.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_gsm.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_mt9234mu.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mts_mt9234zba.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8335_duplex.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366_ap-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8366_ap-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/fmimage_8687.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/helper_8366.fw exists in filesystem
linux-firmware: /usr/lib/firmware/mwl8k/helper_8687.fw exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_eth_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_ethp_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_rss_eth_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myri10ge_rss_ethp_z8e.dat exists in filesystem
linux-firmware: /usr/lib/firmware/myricom/lanai.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ositech/Xilinx7OD.bin exists in filesystem
linux-firmware: /usr/lib/firmware/phanfw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2100_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2200_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2300_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2322_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2400_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ql2500_fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/1040.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/12160.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/1280.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/isp1000.bin exists in filesystem
linux-firmware: /usr/lib/firmware/qlogic/sd7220.fw exists in filesystem
linux-firmware: /usr/lib/firmware/r128/r128_cce.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BARTS_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BARTS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BARTS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/BTC_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAICOS_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAICOS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAICOS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CAYMAN_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CEDAR_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CEDAR_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CEDAR_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CYPRESS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CYPRESS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/CYPRESS_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/JUNIPER_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/JUNIPER_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/JUNIPER_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/PALM_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/PALM_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R100_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R200_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R300_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R420_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R520_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R600_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R600_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R600_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/R700_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/REDWOOD_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/REDWOOD_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/REDWOOD_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS600_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS690_cp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS780_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RS780_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV610_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV610_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV620_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV620_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV630_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV630_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV635_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV635_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV670_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV670_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV710_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV710_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV730_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV730_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV770_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/RV770_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO2_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO2_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/SUMO_rlc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/TURKS_mc.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/TURKS_me.bin exists in filesystem
linux-firmware: /usr/lib/firmware/radeon/TURKS_pfp.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2561.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2561s.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2661.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2860.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt2870.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt3070.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt3071.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt3090.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rt73.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8105e-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168d-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168d-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168e-3.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168f-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8168f-2.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8402-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtl_nic/rtl8411-1.fw exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192cfw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192cufw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192defw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8192sefw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/rtlwifi/rtl8712u.bin exists in filesystem
linux-firmware: /usr/lib/firmware/s2250.fw exists in filesystem
linux-firmware: /usr/lib/firmware/s2250_loader.fw exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/alaw_main.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_capture.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_init.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/ima_adpcm_playback.csp exists in filesystem
linux-firmware: /usr/lib/firmware/sb16/mulaw_main.csp exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/gbdownload.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/gbrcvucode.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/oasisdbgdownload.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/oasisdownload.sys exists in filesystem
linux-firmware: /usr/lib/firmware/slicoss/oasisrcvucode.sys exists in filesystem
linux-firmware: /usr/lib/firmware/sun/cassini.bin exists in filesystem
linux-firmware: /usr/lib/firmware/sxg/saharadbgdownloadB.sys exists in filesystem
linux-firmware: /usr/lib/firmware/sxg/saharadownloadB.sys exists in filesystem
linux-firmware: /usr/lib/firmware/tehuti/bdx.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/TIInit_7.2.31.bts exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw-2.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw-ap.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl1271-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-fw-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-fw-plt-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl127x-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-ap.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw-plt-3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-fw.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl128x-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti-connectivity/wl12xx-nvs.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ti_3410.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ti_5052.fw exists in filesystem
linux-firmware: /usr/lib/firmware/tigon/tg3.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tigon/tg3_tso.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tigon/tg3_tso5.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tlg2300_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/tr_smctr.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ttusb-budget/dspbootcode.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/930-fpga.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMV4p.bin.v2 exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMV9i.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMV9p.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVei.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVeiWO.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVep.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepES.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepES03.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR04.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepFR10.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepIT.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/CMVepWO.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSP4p.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSP9i.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSP9p.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSPei.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/DSPep.bin exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/adi930.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleI.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleII.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleIII.fw exists in filesystem
linux-firmware: /usr/lib/firmware/ueagle-atm/eagleIV.fw exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/Makefile_dux exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/README.dux exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/fx2-include.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/usbdux_firmware.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/usbduxfast_firmware.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux/usbduxsigma_firmware.asm exists in filesystem
linux-firmware: /usr/lib/firmware/usbdux_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/usbduxfast_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/usbduxsigma_firmware.bin exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx231xx-avcore-01.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23418-apu.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23418-cpu.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23418-dig.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23885-avcore-01.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx23885-enc.fw exists in filesystem
linux-firmware: /usr/lib/firmware/v4l-cx25840.fw exists in filesystem
linux-firmware: /usr/lib/firmware/vicam/firmware.fw exists in filesystem
linux-firmware: /usr/lib/firmware/vntwusb.fw exists in filesystem
linux-firmware: /usr/lib/firmware/vxge/X3fw-pxe.ncf exists in filesystem
linux-firmware: /usr/lib/firmware/vxge/X3fw.ncf exists in filesystem
linux-firmware: /usr/lib/firmware/whiteheat.fw exists in filesystem
linux-firmware: /usr/lib/firmware/whiteheat_loader.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yam/1200.bin exists in filesystem
linux-firmware: /usr/lib/firmware/yam/9600.bin exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/ds1_ctrl.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/ds1_dsp.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/ds1e_ctrl.fw exists in filesystem
linux-firmware: /usr/lib/firmware/yamaha/yss225_registers.bin exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.Marvell exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.OLPC exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.agere exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.atheros_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.broadcom_bcm43xx exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.chelsio_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ene_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.i2400m exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.iwlwifi_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.mwl8335 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.myri10ge_firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.phanfw exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.qla2xxx exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ralink-firmware.txt exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.rtlwifi_firmware.txt exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.tda7706-firmware.txt exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ti-connectivity exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.ueagle-atm4-firmware exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.via_vt6656 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENCE.xc5000 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENSE.dib0700 exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/LICENSE.radeon_rlc exists in filesystem
linux-firmware: /usr/share/licenses/linux-firmware/WHENCE exists in filesystem
Errors occurred, no packages were upgraded.
Last edited by Swarfega (2012-05-17 08:59:31)

[SOLVED] pacman error: cannot open package file

Hi
I didn't use my Arch box for a while and today launched it.
I had to install the "p7zip" package, but I'm a "build everything from sources" guy and I tried to install it from source as always. Unsuccessfully: it required nasm.
Decided to install it using pacman, to get it done quickly.
So, I've got the nasm package and uploaded it to my Arch machine (it has no inernet connection, I use NFS to share files).
Executed
pacman -U ./nasm-2.09.10-1-i686.pkg.tar.xz
and for my surprise I've got:
loading package data...
error: './nasm-2.09.10-1-i686.pkg.tar.xz': cannot open package file
Then I tried to run pacman -U for one of "core" packages from the original media (2010.05) and the same result. Some time ago it was working fine.
It gets this error for every file.
The tar.gz file is not broken, I can browse it within Midnigh Commander and get any file .
What could be wrong? Any ideas?
Last edited by art84 (2011-09-16 17:37:33)

@Techman084:
Of course I have ran it in the directory where the package is located. And yes, I also tried to use it with an absolute path like.
@karol
# pacman -V
.--. Pacman v3.3.3 - libalpm v4.0.3
/ _.-' .-. .-. .-. Copyright (C) 2006-2009 Pacman Development Team
\ '-. '-' '-' '-' Copyright (C) 2002-2006 Judd Vinet
This program may be freely redistributed under
the terms of the GNU General Public License.
@the sad clown
1. /var/log/pacman.log
[2010-12-12 13:46] installed kernel26-headers (2.6.33.4-1)
[2010-12-12 14:07] installed r8168 (8.020.00-1)
[2010-12-20 19:33] installed iperf (2.0.5-1)
[2010-12-26 14:46] installed slang (2.2.3-1)
[2010-12-26 15:45] installed mc (4.7.4-1)
2. Why to synchronize? And how? pacman -Syu ?
I have the original 2010.05 distro installed without any updates. Only console. A few packages installed: ethtool, mc, slang, etc. So, I don't need to have it synchronized to the last versions of everythig (if I correctly understood the goal of the sync)
3. I have already that p7zip package on my PC I had to do it manually ... but to be clear, it doesn't work with any package, not only with "p7zip" or "nasm"

Could not open parameter file

Hi everyone,
I was installing oracle 11gr2 on fedora 14 2 weeks
I couldn't find any solve for "could not open parameter file"
I read a lot of forums but I could not
I haven' got any pfile or spfile
I have only $ORACLE_HOME/dbs/init.ora
I haven't got any control file
I installed again again but nothing change
What can I do ?
I set ORACLE_HOME, SID , BASE and LD_LIBRARY_PATH

Sounds like you installed the Oracle software only. What did you install? You might want to run the Database Configuration Assistant (DBCA) to create a database.

Could not open the file

I had worked on the Illustrator CC 2014 with 19 slices of PDF presentation file for my assignment even in 15 minutes ago, and before closing it previous time, I have saved the file, and restarted my laptop, tried to open the PDF file again, but the message of "Could not open the file" was appeared each time I have tried to open it. I wonder what is wrong with it. And I do really have to working on it right now. Here I am attaching the pictures and please solve this problem. Thank you

Does it open in Acrobat?
Did it really complete saving? Or did it crash or did you abort the saving process?
In case you can open it in Acrobat, the PDF part of the file is still intact. Then you could create a niew file in Illustrator and place your file in it. Of course then most editing features will be lost, but at least you've got the content.
Use this script to place all pages at once:
Introducing: Open Multi-Page PDF win/mac

Could not open location 'file:///home/geoff'

I'm using Gnome and after the last update today ( I always do pacman -Syu everyday and accept whatever it gives me in my noobidity ):(
Now I find that when I go to Places--Home Folder and Places--Desktop I get this message.
Could not open location 'file:///home/geoff' (or 'file:///home/geoff/Desktop')
There was an error launching the default action command associated with this location
Have I done something stupid in accepting all updates without question? Or is it something else?
Can you put me on the right learning curve and fix this.
Thanks

I think that the latest udev upgrade has caused the problem. Correct me if I'm wrong.
I did the same upgrade on my laptop and got the same fault.
Apart from the faults in my previous message if I open a terminal over any page I'm looking at, like this for instance, it will not stay "above" the page when the box "only on this workspace" is checked. I have to check "always on top" to make it stay so I can cut and paste things.
When the terminal is minimized in the bottom panel and I click on it, it comes up but the moment I move the mouse pointer to the terminal screen it disappears back to being minimized.
I've never had this weird behavior before.
Hoping someone can help
thanks

Could not open the file in application server

Hi All,
I have a Zreport which will write files on application server. When I tried to download it is showing me "Could not open the file". And when checked again with /nal11 the files does not exist. When I ran the Zreport again the file exist in application server but unable to download. And when checked again the file doesnot exist. Why it is getting archived? Please help me.
Thanks,
Venkata

Hi Sagar,
Below is my file path : /dv2/tmp/instl/salesdata.txt
When I checked in the below path the file exists.
/dv2/tmp/archive/salesdata.txt
Solved the issue.
Thanks,
Venkata

Could not open the file. An internal error occurred.

Hi,
Anyone can solve my problem? Urgent!
I can't open a png file. Others files was ok, just only one file can't open after save.
It show : Could not open the file. An internal error occurred.
Thanks!

Seems like is corrupted during save or was caused by a Fireworks crash.
Try open with another version of Fireworks.
Linus
Fireworks Project Phoenix Product Manager
www.projectphoenix.io
https://www.facebook.com/groups/fwsingapore/
www.twitter.com/chunwui

LRM-00109:could not open parameter file '/u01/app/oracle/product/10.2.0/db

hi
i have manually created a database called ora.i have done all the relative tasks.i can open the database by startup nomount pfile.but when i try to create spfile from pfile, it is showing an error that it is already created.when i give the startup command the
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/10.2.0/db_1/dbs/initora.ora'
above error occurs.acutally my pfile is in another location and it is trying to open it from another loc.ihave added the line
export ORACLE_SID=ora in bashrc file.Already there is one database called orcl and it is also been added to the
bashrc file.
Pz solve it for me.

hi,
>
create spfile='/u01/app/oracle/product/10.2.0/db_1/dbs'
2 from
3 pfile='/u01/app/oracle/product/10.2.0/db_1/admin/ora/pfile/initora.ora';
create spfile='/u01/app/oracle/product/10.2.0/db_1/dbs'
ERROR at line 1:have you startup the database in nomount stage with pfile.. if so.
then
create spfile form pfile='/u01/app/oracle/product/10.2.0/db_1/admin/ora/pfile/initora.ora';
use this command
a spfile will be created inside /dbs/
now restart the DB and give startup command and check the instance status..
as mentioned above export the Oralce_home and Oracle_sid..
regards,
Deepak

ORA-01078: failure in processing system parameters LRM-00109: could not open parameter file '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/initORA11G.ora'

I have installed an Oracle 11gR2 on Oracle Linux Server 6.6 (Virtualbox). I have the users grid and oracle11g. Add groups and install grid infrastructure first as a grid user and install database as oracle user as in documentation successfully.
I have following users and groups as
[grid@orcl11g ~]$ id grid
   uid=501(grid) gid=502(oinstall) groups=502(oinstall),492(vboxsf),501(grid),503(dba),505(asmdba),506(asmadmin),507(asmoper)
[grid@orcl11g ~]$ id oracle11g
   uid=500(oracle11g) gid=502(oinstall) groups=502(oinstall),500(oracle11g),492(vboxsf),503(dba),504(oper),505(asmdba)
.bash_profile edited for oracle11g user as
"export TMP=/tmp
export ORACLE_HOSTNAME=orcl11g
export ORACLE_UNQNAME=ora11g
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1
export ORACLE_SID=ora11g
export PATH=$PATH:$ORACLE_HOME/bin
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib;
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib;
.bash_profile edited for grid user as
"export TMP=/tmp
export ORACLE_HOSTNAME=orcl11g
export ORACLE_UNQNAME=+ASM
export ORACLE_BASE=/u01/app/grid
export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/grid
export GRID_HOME=$ORACLE_BASE/product/11.2.0/grid
export ORACLE_SID=+ASM
export PATH=$PATH:$ORACLE_HOME/bin
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib;
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib;
When I log on as grid user. I check the followings:
[grid@orcl11g ~]$ crsctl check has
CRS-4638: Oracle High Availability Services is online
[grid@orcl11g ~]$ srvctl status database -d ora11g
Database is running.
[grid@orcl11g ~]$ sqlplus sys as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 25 19:17:37 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Automatic Storage Management option
SQL> select status from v$instance;
STATUS
STARTED
Till here everything seems to be OK!!!!
When I log as oracle user. I check the followings:
[oracle11g@orcl11g ~]$ sqlplus sys as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 25 19:21:46 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Enter password:
Connected to an idle instance.
SQL> select status from v$instance;
select status from v$instance
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0
SQL> startup
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/initORA11G.ora'
Also when I log on as a grid user again and use following commands to shutdown and start database again the STATUS of instance is again STARTED not OPEN.
[grid@orcl11g ~]$ srvctl stop database -d ora11g -o normal
[grid@orcl11g ~]$ srvctl start database -d ora11g
And also when I edit /etc/oratab file. I change N to Y for +ASM. But when restart system it seems not changed value is N again.
    +ASM:/u01/app/grid/product/11.2.0/grid:N   # line added by Agent
     ora11g:/u01/app/oracle/product/11.2.0/dbhome_1:Y
NOW QUESTIONS!!!!!
1. Why I can't change the status of database to OPEN as grid user?
2. The status is always STARTED when querying v$instance. İs it status of +ASM or database?
3. When checking database as grid user it seems to be Database runnning... If running why it is not in OPEN state? What is running means here?
4. When I log on as oracle user and query v$instance, then error shown above occured. And also when startup the database then another error occured as in above. WHY?
5. When I edit /etc/oratab file manually why second row saved but the first one is changed after restart the system?
6. Normally, which user have to start, stop or manage database? I think that oracle user is necessary for managing database and the grid user is only for managing ASM and Oracle Restart.
PLEASE HELP ME TO SOLVE THIS CHAOTİC SİTUATİON!!!
Thanks,
DBA_84

I have installed an Oracle 11gR2 on Oracle Linux Server 6.6 (Virtualbox)
Pl identify exact version of 11gR2 to 4 decimal places. As noted in your other thread - Failed to start oracle-ohasd, error: Inappropriate ioctl for device ohasd failed to start at roothas.pl - you will need a minimum version of 11.2.0.3 for Linux 6.x - using a lower version may result in unexpected issues or problems.

Could not open the file. Not enough memory

I have always used fireworks cs4 normally, but today, i experienced a bit of trouble. there is one png file that when i click to open it the fireworks loads but then a message pops up (could not open the file. Not enough memory) after a bit of researching, i found out that this error happens when i bring to stage one of the common libraries menu bars. (menu bar 4). Does anyone know how to fix this?
ps: I am able to open this file via file-open-*png. Please i really need help. Is the library corrupted maybe?

Hi,
It opened on mine (1.2Gb). I don't think it's a memory issue. I've used FWCS4 with 512mb RAM, never had such a problem. (of course it was very slow at the start, and i used to leave for a cup of coffee first and then come back when it was ready for work. That's why i upgraded to 1.2G .)
Import this menu bar from the common library, save it again as a png and then open it with fireworks the way you did, to see if the same error occurs.
Has this happened with other files as well?

Safari Crash / Could not open cookie file Cookies.plist for reading

Hi everyone
I dont know why my Safari is Crashing, I review the console and I find this line:
Help... I dont how to solve the problem...
*ntlmRand failed to open /dev/random
2007-01-26 23:48:55.004 Safari[8953] Could not open cookie file "/Users/scanner9/Library/Cookies/Cookies.plist" for reading.
2007-01-27 00:00:53.553 Safari[8953] Could not open cookie file "/Users/scanner9/Library/Cookies/Cookies.plist" for reading.
2007-01-27 00:01:16.915 Safari[8953] -[BrowserWindowController loadWindow]: failed to load window nib file '/Applications/Safari.app/Contents/Resources/English.lproj/Browser.nib'.
2007-01-27 00:01:16.923 Safari[8953] Cannot load Interface Builder file 'NSAlertPanel'
Thanks.

jhpereze,
Quit Safari, find the Cookies.plist file in your Macintosh HD/Users/yourusername/Library/Cookies folder, drag it to your Desktop, log out/in or restart and let us know what happens.
If that is unsuccessful post your Safari crash log for further analysis.
;~)

Could not open include file "math.h"

I installed Sun ONE 7.0 on Solaris 8, and write a simple program to test it.
#include <list>
using namespace std;
int main(int argc, char* argv[])
list<char *> ll;
#CC test.cc
But the error occurs:
"/sysadm/c7.0/SUNWspro/prod/include/CC/std/math.h", line 9: Error: Could not open include file "math.h".
I cannot find "math.h" in /usr/include, but can find it in following directory
/sysadm/c7.0/SUNWspro/prod/include/CC/Cstd/rw/math.h
/sysadm/c7.0/SUNWspro/prod/include/CC/std/math.h
/sysadm/c7.0/SUNWspro/prod/include/CC/stlport4/math.h
Do I missing any library and configuration?
Appreciate any help.

I installed Sun ONE 7.0 on Solaris 8, and write a
simple program to test it.
#include <list>
using namespace std;
int main(int argc, char* argv[])
list<char *> ll;
#CC test.cc
But the error occurs:
"/sysadm/c7.0/SUNWspro/prod/include/CC/std/math.h",
line 9: Error: Could not open include file "math.h".
I cannot find "math.h" in /usr/include, but can find
it in following directory
/sysadm/c7.0/SUNWspro/prod/include/CC/Cstd/rw/math.h
/sysadm/c7.0/SUNWspro/prod/include/CC/std/math.h
/sysadm/c7.0/SUNWspro/prod/include/CC/stlport4/math.h
Do I missing any library and configuration?It looks like you didn't do a full install (or else removed some packages).
/usr/include/math.h is part of SUNWlibm
A bientot
Paul

RSCRM 085 Could not open the file

HI Guru's,
for two weeks we have trouble on RSCRM BAPI. we have a job which execute the function module to generate a file. yesterday we applied an OSS Note to solved the problem RSCRM164.
But now if i execute my process by the program i have the error RSCRM085 could not open the file.
If i execute the process by the transaction RSCRM_BAPI (with the same parameter) the generation is successfull.
Do you have an idea what problem i have ?
Thanks
CYril

Hello Cyril,
If you regenerate the coding and reactivate the program does it resolve the issue?
Best Regards,
Des

Fireworks CS4: could not open the file. Unknown file type

Hello, this is the second file created with Fireworks CS4 that can't be opened. I'm using the same Fireworks installation that created the file. The file is a 1.2 MB file containing the pages of a draft for a new website.
When I click on the file in Windows Explorer to open it, Fireworks tries to open it, but it can't. Instead, an alert pops up with this message: "Adobe Fireworks CS4 Could not open the file. Unknown file type"
Working with Windows Vista Business, Adobe Web Premium CS4 suite
I already tried opening the file, to no avail, with:
-another computer with Windows XP Pro SP3 and the same Fireworks version
-another computer with Windows XP Pro SP3 and Fireworks CS3
-another computer with Windows XP Pro SP3 and Fireworks MX 2004
Please help.

I tried to find a solution for you by using:
http://www.adobe.com/cfusion/search/index.cfm?loc=en_us&term=error%20opening%20file&cat=su pport&product=fireworks
but I couldn't find anything. You may want to give it a go :-)
Can you open the file in another program, maybe an earlier version of FWs, or Photoshop or even Illustrator if you have it?
Not sure if there's a configuration folder that needs to be renamed and when FWs restarts it re-writes the config file... that's something to has to be done with DW when 'funny stuff' happens.
That's the best advice I have, I'm sorry :-(
Nadia
Adobe® Community Expert : Dreamweaver
Unique CSS Templates |Tutorials |SEO Articles
http://www.DreamweaverResources.com
Book: Ultimate CSS Reference
http://www.sitepoint.com/launch/005dfd4/3/133
http://twitter.com/nadiap

Maybe solved pacman : could not open package: File too large

Similar Messages

Maybe you are looking for