Latest Bugs & Tasks

Syndicate content Haiku
Trac Timeline
Updated: 56 min 10 sec ago

Ticket #3918 (Keymap preferences should save selected keyboard layout.) closed

Fri, 2016-08-12 20:19
fixed:

This bug has been fixed for a long time now.

Categories: Development

Ticket #12910 (Haiku x86-64 build won't build itself) created

Fri, 2016-08-12 18:57

Latest Revision (as of 8/8/16). It doesn't stop at interrupt.o anymore, but stops at boot_loader_bios_ia32, which I assume basically means the same thing?

My question is, if you can build Haiku x86-64 in another OS (which is bootable, since I download bootable versions (.iso and .raw) now and then), why can't you build a bootable version within Haiku x86-64 itself? Can't you just modify the code to make the build work within Haiku x86-64 itself?

How much would need to be donated to to allow complete building of Haiku x86-64 from within Haiku x86-64 once again (which worked many years ago, because I was doing it)?

Relevant output shown below:

Welcome to the Haiku shell.

~> cd haiku/haiku
~/haiku/haiku> jam -q haiku-anyboot-image
Starting build of type regular ...
qrencode support not available on x86_64
/boot/home/haiku/haiku/src/add-ons/kernel/debugger/disasm/x86_64/Jamfile: No such file or directory
/boot/home/haiku/haiku/src/bin/debug/ltrace/arch/x86_64/Jamfile: No such file or directory
Skipping setjmp_test2.S test on non-x86
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...found 138005 target(s)...
...updating 12981 target(s)...
MkDir1 /boot/home/haiku/haiku/generated/objects/haiku_host/x86_64/release/tools/anyboot
C++ /boot/home/haiku/haiku/generated/objects/haiku_host/x86_64/release/tools/anyboot/anyboot.o
Link /boot/home/haiku/haiku/generated/objects/haiku_host/x86_64/release/tools/anyboot/anyboot
Chmod1 /boot/home/haiku/haiku/generated/objects/haiku_host/x86_64/release/tools/anyboot/anyboot
BootLd /boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_loader_bios_ia32
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `BIOSDrive::WriteAt(void*, long long, void const*, unsigned long)':
(.text+0xf48): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `BIOSDrive::WriteAt(void*, long long, void const*, unsigned long)':
(.text+0xf79): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `BIOSDrive::ReadAt(void*, long long, void*, unsigned long)':
(.text+0x1128): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `BIOSDrive::ReadAt(void*, long long, void*, unsigned long)':
(.text+0x1143): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `BIOSDrive::ReadAt(void*, long long, void*, unsigned long)':
(.text+0x11b2): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `BIOSDrive::ReadAt(void*, long long, void*, unsigned long)':
(.text+0x11c8): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `add_block_devices(DoublyLinkedList<Node, DoublyLinkedListStandardGetLink<Node> >*, bool) [clone .part.9]':
devices.cpp:(.text+0x1c9c): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o: In function `cpu_init':
(.text+0x3434): undefined reference to `udivdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_partitions.a(efi_gpt.o): In function `efi_gpt_identify_partition(int, partition_data*, void)':
efi_gpt.cpp:(.text+0x2ce): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_partitions.a(PartitionMap.o): In function `Partition::CheckLocation(long long) const':
PartitionMap.cpp:(.text+0x56f): undefined reference to `moddi3'
PartitionMap.cpp:(.text+0x58f): undefined reference to `moddi3'
PartitionMap.cpp:(.text+0x5c5): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_partitions.a(PartitionMap.o): In function `PrimaryPartition::GetPartitionDescriptor(partition_descriptor*) const':
PartitionMap.cpp:(.text+0x8b1): undefined reference to `divdi3'
PartitionMap.cpp:(.text+0x8cb): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_partitions.a(PartitionMap.o): In function `LogicalPartition::GetPartitionDescriptor(partition_descriptor*, bool) const':
PartitionMap.cpp:(.text+0xcfa): undefined reference to `divdi3'
PartitionMap.cpp:(.text+0xd1a): undefined reference to `divdi3'
PartitionMap.cpp:(.text+0xd65): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/bfs/boot_bfs.a(bfs.o):bfs.cpp:(.text+0xe8): more undefined references to `divdi3' follow
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/bfs/boot_bfs.a(Stream.o): In function `BFS::Stream::FindBlockRun(long long, BFS::block_run&, long long&)':
Stream.cpp:(.text+0x766): undefined reference to `moddi3'
Stream.cpp:(.text+0x77a): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/bfs/boot_bfs.a(Stream.o): In function `BFS::Stream::ReadAt(long long, unsigned char*, unsigned long*)':
Stream.cpp:(.text+0x9b1): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/bfs/boot_bfs.a(BPlusTree.o): In function `BFS::bplustree_header::IsValid() const [clone .part.7]':
BPlusTree.cpp:(.text+0x21): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/bfs/boot_bfs.a(BPlusTree.o): In function `BFS::CachedNode::InternalSetTo(BFS::Transaction*, long long)':
BPlusTree.cpp:(.text+0x173): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/bfs/boot_bfs.a(BPlusTree.o): In function `BFS::CachedNode::SetTo(long long, BFS::bplustree_node const, bool)':
BPlusTree.cpp:(.text+0x344): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Volume.o): In function `FATFS::Volume::_ClusterAllocated(unsigned long) [clone .part.9]':
Volume.cpp:(.text+0x2e): undefined reference to `divdi3'
Volume.cpp:(.text+0x5a): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Volume.o): In function `FATFS::Volume::NextCluster(unsigned long, unsigned long)':
Volume.cpp:(.text+0x646): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Volume.o): In function `FATFS::Volume::_UpdateCluster(unsigned long, unsigned long)':
Volume.cpp:(.text+0x79b): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Directory.o): In function `FATFS::Directory::UpdateDirEntry(FATFS::Volume&, long long, unsigned long, unsigned long)':
Directory.cpp:(.text+0x758): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Directory.o): In function `FATFS::Directory::_AddEntry(FATFS::dir_entry&, long long&)':
Directory.cpp:(.text+0xbf1): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Stream.o): In function `FATFS::Stream::Stream(FATFS::Volume&, unsigned long, long long, char const*)':
Stream.cpp:(.text+0x8f): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Stream.o): In function `FATFS::Stream::_FindCluster(long long, unsigned long&)':
Stream.cpp:(.text+0x2ba): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Stream.o): In function `FATFS::Stream::_FindOrCreateCluster(long long, unsigned long&, bool&)':
Stream.cpp:(.text+0x44d): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Stream.o): In function `FATFS::Stream::FindBlock(long long, long long&, long long&)':
Stream.cpp:(.text+0x59d): undefined reference to `moddi3'
Stream.cpp:(.text+0x5e6): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Stream.o): In function `FATFS::Stream::ReadAt(long long, void*, unsigned long*, long long*)':
Stream.cpp:(.text+0x6cb): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a(Stream.o): In function `FATFS::Stream::WriteAt(long long, void const*, unsigned long*, long long*)':
Stream.cpp:(.text+0xa34): undefined reference to `moddi3'
Stream.cpp:(.text+0xa90): undefined reference to `moddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_loader.a(DataIO.o): In function `BMallocIO::SetSize(long long)':
DataIO.cpp:(.text+0x5c8): undefined reference to `divdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o: In function `number(Buffer&, unsigned long long, unsigned long, int, int, int)':
kernel_vsprintf.cpp:(.text+0xdf3): undefined reference to `umoddi3'
kernel_vsprintf.cpp:(.text+0xe08): undefined reference to `udivdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o: In function `vsnprintf':
(.text+0x14bf): undefined reference to `umoddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o: In function `vsnprintf':
(.text+0x1897): undefined reference to `umoddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o: In function `vsnprintf':
(.text+0x1903): undefined reference to `umoddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o: In function `vsnprintf':
(.text+0x1916): undefined reference to `udivdi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o: In function `vsnprintf':
(.text+0x195d): undefined reference to `umoddi3'
/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o: In function `vsnprintf':
(.text+0x1973): undefined reference to `udivdi3'

ld -Bstatic --script=/boot/home/haiku/haiku/src/system/ldscripts/x86_64/boot_loader_bios_ia32.ld -o "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_loader_bios_ia32" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/platform/bios_ia32/boot_platform_bios_ia32.o" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/arch/x86/boot_arch_x86.o" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_loader.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/net/boot_net.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_partitions.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/bfs/boot_bfs.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/amiga_ffs/boot_amiga_ffs.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/tarfs/boot_tarfs.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/fat/boot_fatfs.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/packagefs/boot_packagefs.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/boot_loader.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/loader/file_systems/tarfs/boot_zlib.a" "/boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_libroot.o" /boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/5.4.0/libsupc++.a /boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/5.4.0/libgcc.a \

...failed BootLd /boot/home/haiku/haiku/generated/objects/haiku/x86_64/release/system/boot/boot_loader_bios_ia32 ...

BUILD FAILURE:
...failed updating 1 target(s)...
...skipped 4 target(s)...
...updated 3 target(s)...
~/haiku/haiku>

Categories: Development

Ticket #12909 (Package Installer installs to wrong directory) created

Wed, 2016-08-10 18:41

hrev50481 x86_gcc2
Did a fresh Haiku install and tried to install GoBe productive
Installer points to "/boot/system/non-packaged/apps"
However, package is installed to "/boot/home/" instead
hrev50418 is working correctly, hrev50451 and later are broken
Possible culprits appear to be hrev50447 or hrev50448

Categories: Development

Ticket #12907 (compiling llvm with GCC 5.4.0) closed

Wed, 2016-08-10 05:29
no change required:

Seems memory is lacking:
*check your virtual memory settings (at least 2GB virtual memory)
*when in a VM check it has enough memory (ie 2GB physical RAM)
*check the build doesn't happen with too many jobs (-j argument ie -j2).

Unless I'm mistaken, this doesn't require a change to Haiku.

Categories: Development

Ticket #12908 (Team Monitor UI - bad buttons position) created

Wed, 2016-08-10 05:01

Whenever calling team monitor, both "Force reboot" and "Cancel" buttons are out of the window.

Categories: Development

Ticket #12907 (compiling llvm with GCC 5.4.0) created

Wed, 2016-08-10 04:56

Hi,

When compiling llvm under Haiku (gcc2 hybrid and x64), I have the following error.

/boot/system/develop/tools/x86/bin/../lib/gcc/i586-pc-haiku/5.4.0/../../../../i586-pc-haiku/bin/ld: failed to set dynamic section sizes: Memory exhausted
collect2: error: ld returned 1 exit status
tools/lto/CMakeFiles/LTO.dir/build.make:254: recipe for target 'lib/libLTO.so' failed
make[2]: * [lib/libLTO.so] Error 1
CMakeFiles/Makefile2:12990: recipe for target 'tools/lto/CMakeFiles/LTO.dir/all' failed
make[1]:
* [tools/lto/CMakeFiles/LTO.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: * [all] Error 2

Categories: Development

Ticket #12906 (pkgman install checksum error) created

Wed, 2016-08-10 04:53

Hi,

When using the pkgman command install I have the following error:

/Storage/dev/llvm> pkgman install subversion
Downloading repochecksum-1...done.
Validating checksum for Haiku...done.
Downloading repocache-2...done.
Checksum error:
*** expected '<?xml version="1.0" encoding="UTF-8"?>
*** <!DOCTYPE html PUBLIC "-/'
*** got      'e49d399c4740a8de7404a2c9c3885357706f6e1e0a93328740df11dcd7ba0a5c'*** aborted : No Error (1701273973)
Validating checksum for Haiku.../Storage/dev/llvm>
/Storage/dev/llvm>

While it is possible to install the package in HaikuDepot.

Categories: Development

Ticket #12905 (package_repo requires a url in repo-info file which needs eval) created

Wed, 2016-08-10 03:38

package_repo requires a url in the repo.info file. (the repo.info file is read in by package_repo tool to build the binary on-disk repo which is then served by http to our package manager)

This really doesn't make sense. You're always going to know the repo's base url... so why would you need to specify it while building the repo?

This makes repo creation a lot more complex than it needs to be... I also haven't been able to find anywhere the repo.info url is actually used. (don't get a packages's URL mixed up the internal repo url)

Example:

URL: ​http://packages.haiku-os.org/haikuports/master/repo/x86_64/c623cf2b4d85bc452d5a21a2586e552fe1b04f6d66eca0663f257461c106db9f/repo.info

name HaikuPorts
vendor "Haiku Project"
summary "The HaikuPorts repository (for Haiku hrev50482)"
priority 1
url http://packages.haiku-os.org/haikuports/master/repo/x86_64/c623cf2b4d85bc452d5a21a2586e552fe1b04f6d66eca0663f257461c106db9f
architecture x86_64
Categories: Development

Ticket #12904 (64 bit application crashes) created

Mon, 2016-08-08 20:22

hrev50481 x86_64
Copied anyboot image to CD rom and did fresh install
Vision crashed on quit, and created debug report (attached)
StyledEdit crashed on quit, after reading previous debug report. Debug report attached.

Categories: Development

Ticket #12903 (64 bit installer crash) created

Mon, 2016-08-08 20:17

hrev50481 x86_64
Copied anyboot image to CD rom and boot to installer
Installer KDL's on the first dialog window (IMG_0198.JPG attached)
Syslog and previous syslog attached

Categories: Development

Ticket #12902 (Driver for ICE1724 based soundcards. (ESI Juli@)) created

Mon, 2016-08-08 19:47

If possible, I'd like to request a driver for this chipset, which my soundcard is based upon.
Here is the product page: ​http://www.esi-audio.com/products/julia/

It is well supported in ALSA and it lists linux compatability in the product page, but it will not work in Haiku.

Linux uses the driver snd-ice1724

Device name: VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller
Manufacturer: VIA Technologies Inc.

device/type 0x4
device/subtype 0x1
device/interface 0
device/vendor 0x1412
device/id 0x1724

Class info Multimedia controller (Multimedia audio controller)
Device name VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller
Device paths Not implemented
device/bus pci
device/flags 1
device/id 0x1724
device/interface 0
device/subtype 0x1
device/type 0x4
device/vendor 0x1412
Driver used Not implemented
Manufacturer VIA Technologies Inc.
pci/bus 4
pci/device 5
pci/domain 0
pci/function 0

Categories: Development

Ticket #12901 ([launch_daemon] Does not detect that it is already running and starts ...) created

Mon, 2016-08-08 15:35
  1. Go to /system/servers
  2. Double-click launch_daemon
  3. It appears another app_server is started on top of the existing one, which causes all sorts of weird glitches and 100% CPU usage on all cores.
Categories: Development

Ticket #12900 (Booting usb 3 flash drive on usb 3 port kdl and freeze) closed

Sat, 2016-08-06 11:42
duplicate:

I experience the same, see #12895.

Categories: Development

Ticket #12900 (Booting usb 3 flash drive on usb 3 port kdl and freeze) created

Sat, 2016-08-06 02:35

Booting a usb 3 flash drive always does a kdl at the middle boot icon. I cannot type anything into the kdl screen because it is frozen. If I boot the same drive on usb 2 port there is no kdl. I was testing with hrev50464 gcc4 hybrid

Categories: Development

Ticket #12899 (Use fluidlite as fluidsynth replacement, add SF3 support) created

Thu, 2016-08-04 18:13

Fluidlite is a "very light version of FluidSynth designed to be hardware, platform and external dependency independant".

I uploaded packages for it and am proposing a patch to switch to it:

  • add build features for libvorbis and fluidlite
  • use these libs and headers for libmidi.
  • include <fluidlite.h> instead of <fluidsynth.h>

The functionality should be the same as now, but I could only basically test.
The bootstrap build (which doesn't include libmidi.so) isn't affected.

  • libvorbis is required to support SF3 (SF2 files compressed with ogg vorbis).
  • To be noticed, the fluidlite packages include this commit from Pete added in hrev45742.
  • I didn't manage to have a single build feature with the 2 libs, in fact because fluidlite is only a static library, linking against libvorbisfile.so had to be added.
  • SF3 support could help to use better quality soundfounds for a same disksize (MuseScore provides FluidR3Mono_GM.sf3 for instance).
  • Fluidsynth seems to be stagnant (4 years without a release, well that's more than Haiku :) ).

Comments welcome! I plan to push the change for real world test next week.

diff --git a/build/jam/BuildFeatures b/build/jam/BuildFeatures
index 0b75ec3..660ee57 100644
--- a/build/jam/BuildFeatures
+++ b/build/jam/BuildFeatures
@@ -256,6 +256,37 @@ if [ IsPackageAvailable ffmpeg_devel ] {
 }
+# Fluidlite
+if [ IsPackageAvailable fluidlite_devel ] && [ IsPackageAvailable libvorbis_devel ] {
+	ExtractBuildFeatureArchives fluidlite :
+		file: devel fluidlite_devel
+			library: $(developLibDir)/libfluidlite.a
+			headers: $(developHeadersDir)
+		;
+
+	EnableBuildFeatures fluidlite ;
+} else {
+	Echo "Fluidlite support not available on $(TARGET_PACKAGING_ARCH)" ;
+}
+
+
+# Libvorbis
+if [ IsPackageAvailable libvorbis_devel ] {
+	ExtractBuildFeatureArchives libvorbis :
+		file: base libvorbis
+			runtime: lib
+		file: devel libvorbis_devel
+			depends: base
+			library: $(developLibDir)/libvorbisfile.so.3
+			headers: $(developHeadersDir)
+		;
+
+	EnableBuildFeatures libvorbis ;
+} else {
+	Echo "Libvorbis support not available on $(TARGET_PACKAGING_ARCH)" ;
+}
+
+
 # Freetype
 if [ IsPackageAvailable freetype_devel ] {
 	ExtractBuildFeatureArchives freetype :
diff --git a/src/kits/midi/Jamfile b/src/kits/midi/Jamfile
index d6bb5c2..d91a03a 100644
--- a/src/kits/midi/Jamfile
+++ b/src/kits/midi/Jamfile
@@ -9,11 +9,20 @@ if $(TARGET_PLATFORM) != haiku {
 }
 UsePrivateHeaders midi ;
-UseLibraryHeaders fluidsynth ;
+
 local architectureObject ;
 for architectureObject in [ MultiArchSubDirSetup ] {
 	on $(architectureObject) {
+		if ! [ FIsBuildFeatureEnabled fluidlite ] {
+			continue ;
+		}
+
+		UseBuildFeatureHeaders fluidlite ;
+		Includes [ FGristFiles MidiSynth.cpp MidiSynthFile.cpp
+			SoftSynth.cpp Synth.cpp ]
+			: [ BuildFeatureAttribute fluidlite : headers ] ;
+
 		SharedLibrary [ MultiArchDefaultGristFiles libmidi.so ] :
 			Midi.cpp
 			MidiGlue.cpp
@@ -30,7 +39,8 @@ for architectureObject in [ MultiArchSubDirSetup ] {
 			be
 			midi2
 			media
-			[ MultiArchDefaultGristFiles libfluidsynth.so ]
+			[ BuildFeatureAttribute libvorbis : library ]
+			[ BuildFeatureAttribute fluidlite : library ]
 			[ TargetLibsupc++ ]
 			;
 	}
diff --git a/src/kits/midi/SoftSynth.h b/src/kits/midi/SoftSynth.h
index ccd7cb4..da9c7a8 100644
--- a/src/kits/midi/SoftSynth.h
+++ b/src/kits/midi/SoftSynth.h
@@ -19,7 +19,7 @@
 	This version of SoftSynth is a wrapper libfluidsynth.so.
  */
-#include <fluidsynth.h>
+#include <fluidlite.h>
 #include <Midi.h>
 #include <SoundPlayer.h>
 #include <Synth.h>
Categories: Development

Ticket #12898 (iSCSI initiator support) created

Tue, 2016-08-02 14:59

Lots of NAS devices these days have iSCSI target support. Adding support for Haiku to be an iSCSI initiator could open additional development and user use applications under Haiku.

NetBSD has a fairly simple initiator that is under a MIT compatible license (attached, obtained from ​ftp://ftp.fi.netbsd.org/pub/NetBSD/packages/distfiles/)

An iSCSI initiator presents the remote block device locally. It isn't a filesystem but binding the block device over the network to the local host. Only one host can generally use an iSCSI target at a time (unless you're using a clustering filesystem like GPFS or OCFS)

iSCSI initiator boot support was added in #5319 for PPC

Categories: Development

Ticket #12897 (Connections in Cortex are not working sometimes) created

Mon, 2016-08-01 15:02

This is hrev50463.
In some cases connecting nodes is Cortex are successful, but actually not working. This connections are disappear after restarting Cortex.
Test cases:

  1. Connect line in to mixer. Listening line in is expected, but I don't hear it. Recording line in by SoundRecorder is working.
  2. Disconnect mixer and audio output and connect again. Sound is not working anymore. Restarting media services doesn't help. Only reboot recovers sound.

I don't know is it Cortex bug or bug in media system.

Categories: Development

Ticket #12896 (Failed to mount system packagefs: Out of memory with 128 GB RAM) created

Mon, 2016-08-01 12:00

This system boots past packagefs thing when memory is limited to 4 GB.

Can't get more info from KDL as keyboard doesn't work there. No serial debug possible either.

Categories: Development