Turns out Vigra was not healthy working anymore. Cannot make it work so disabled it and used sudo port install vigra instead which works. Seems I have it working and standalone for arm64 atm but will do more tests.
söndag 7 maj 2023 kl. 11:39:36 UTC+2 skrev dudek53: > Having issue again, go figure :). > Compiling fine but getting segmentations faults and also something called > Bus error 10 when running align_image_stack, > > Opening up hugin I am getting this error code. Just putting it out there > for checking. I am building upon Erkans changes. His versions works just > fine, mine do not :). > <?xml version="1.0" encoding="UTF-8"?> > <report version="1.0" kind="exception"> > <system description="macOS Version 13.3.1 (Build 22E261)"/> > <stack> > <frame level="0" function="wxFatalSignalHandler(int)" offset="0" > address="0x10231b2b0"/> > <frame level="1" function="_sigtramp" offset="0" > address="0x183646a84"/> > <frame level="2" > function="vigra::JPEGDecoderImpl::JPEGDecoderImpl(std::__1::basic_string<char, > > std::__1::char_traits<char>, std::__1::allocator<char>> > const&)" offset="0" address="0x1008f9884"/> > <frame level="3" > function="vigra::JPEGDecoderImpl::JPEGDecoderImpl(std::__1::basic_string<char, > > std::__1::char_traits<char>, std::__1::allocator<char>> > const&)" offset="0" address="0x1008f9884"/> > <frame level="4" > function="vigra::JPEGDecoder::init(std::__1::basic_string<char, > std::__1::char_traits<char>, std::__1::allocator<char>> > const&)" offset="0" address="0x1008f9cb8"/> > <frame level="5" > function="vigra::CodecManager::getDecoder(std::__1::basic_string<char, > std::__1::char_traits<char>, std::__1::allocator<char>> > const&, std::__1::basic_string<char, > std::__1::char_traits<char>, std::__1::allocator<char>> > const&, unsigned int) const" offset="0" address="0x1008e4200"/> > <frame level="6" function="vigra::ImageImportInfo::readHeader_()" > offset="0" address="0x1008f3cdc"/> > <frame level="7" > function="vigra::ImageImportInfo::ImageImportInfo(char const*, unsigned > int)" offset="0" address="0x1008f3bfc"/> > <frame level="8" > function="PanoCommand::wxAddImagesCmd::processPanorama(HuginBase::Panorama&)" > > offset="0" address="0x101187bd4"/> > <frame level="9" > function="PanoCommand::CombinedPanoCommand::processPanorama(HuginBase::Panorama&)" > > offset="0" address="0x10117ca7c"/> > <frame level="10" function="PanoCommand::PanoCommand::execute()" > offset="0" address="0x10117c710"/> > <frame level="11" > function="PanoCommand::CommandHistory::addCommand(PanoCommand::PanoCommand*, > bool)" offset="0" address="0x10119fb08"/> > <frame level="12" function="PanoDropTarget::OnDropFiles(int, int, > wxArrayString const&)" offset="0" address="0x1003f58bc"/> > <frame level="13" function="wxFileDropTarget::OnData(int, int, > wxDragResult)" offset="0" address="0x10247a638"/> > <frame level="14" > function="wxWidgetCocoaImpl::performDragOperation(void*, NSView*, void*)" > offset="0" address="0x10241bde4"/> > <frame level="15" function="wxOSX_performDragOperation(objc_object*, > objc_selector*, id<NSDraggingInfo>)" offset="0" > address="0x10241ad4c"/> > <frame level="16" function="NSCoreDragReceiveMessageProc" offset="0" > address="0x186ba6aa0"/> > <frame level="17" function="CallReceiveMessageCollectionWithMessage" > offset="0" address="0x188e73c14"/> > <frame level="18" function="DoMultipartDropMessage" offset="0" > address="0x188e6dc94"/> > <frame level="19" function="DoDropMessage" offset="0" > address="0x188e6da4c"/> > <frame level="20" function="CoreDragMessageHandler" offset="0" > address="0x188e717ec"/> > <frame level="21" function="__CFMessagePortPerform" offset="0" > address="0x18379af24"/> > <frame level="22" > function="__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__" > offset="0" address="0x1836f6ca0"/> > <frame level="23" function="__CFRunLoopDoSource1" offset="0" > address="0x1836f6bc0"/> > <frame level="24" function="__CFRunLoopRun" offset="0" > address="0x1836f55a0"/> > <frame level="25" function="CFRunLoopRunSpecific" offset="0" > address="0x1836f458c"/> > <frame level="26" function="RunCurrentEventLoopInMode" offset="0" > address="0x18cf29df4"/> > <frame level="27" function="ReceiveNextEventCommon" offset="0" > address="0x18cf29c30"/> > <frame level="28" > function="_BlockUntilNextEventMatchingListInModeWithFilter" offset="0" > address="0x18cf29988"/> > <frame level="29" function="_DPSNextEvent" offset="0" > address="0x186913f58"/> > <frame level="30" function="-[NSApplication(NSEvent) > _nextEventMatchingEventMask:untilDate:inMode:dequeue:]" offset="0" > address="0x1869130f4"/> > <frame level="31" function="-[NSApplication run]" offset="0" > address="0x186907558"/> > <frame level="32" function="wxGUIEventLoop::OSXDoRun()" offset="0" > address="0x1023ed6ec"/> > <frame level="33" function="wxCFEventLoop::DoRun()" offset="0" > address="0x102307450"/> > <frame level="34" function="wxEventLoopBase::Run()" offset="0" > address="0x1022741c4"/> > <frame level="35" function="wxAppConsoleBase::MainLoop()" offset="0" > address="0x10224e450"/> > <frame level="36" function="wxApp::OnRun()" offset="0" > address="0x10238b494"/> > <frame level="37" function="wxEntry(int&, wchar_t**)" offset="0" > address="0x1022a0018"/> > <frame level="38" function="main" offset="0" address="0x1003ed2ac"/> > <frame level="39" function="start" offset="0" address="0x1832bff28"/> > </stack> > </report> > > söndag 7 maj 2023 kl. 10:37:29 UTC+2 skrev dudek53: > >> All good if you ask me 👍. >> >> Den sön 7 maj 2023 08:11Luís Henrique Camargo Quiroz <lui...@gmail.com> >> skrev: >> >>> >>> Hi, >>> >>> Just to say that for beginners it may seem confusing how to use git >>> or mercurial, start a new branch, etc. I think that anything done so far >>> was in the best intention to help, especially for those with Macs. >>> I don't think that Tomas meant to be heavy on negativity, nor with >>> intent of discouraging anyone, but an alert to be double cautious, because >>> of the problems we can create in git/mercurial/others -- I myself have >>> never found a concise and perfectly understandable guide on how to use >>> these programs. And while adventuring to fix software from others made many >>> mistakes too, because there were lots of things I was ignorant about. I >>> ever had to spend time, months maybe, until I knew what was the right thing >>> to do. >>> >>> nice weekend! >>> >>> Luís Henrique >>> >>> Em sex., 5 de mai. de 2023 às 12:40, dudek53 <dud...@gmail.com> >>> escreveu: >>> >>>> Regarding the numbers that fixed my issue. Could you suggest a way to >>>> verify the validity of the fix? I tested it on 5-6 different workstations >>>> with different people having the same issue and the fix fully worked on >>>> all >>>> stations. I sincerely would like to get the fix reviewed from the code >>>> author or someone with knowledge in this are but I would need some help >>>> here to find out the right person to ask. >>>> Meanwhile. Any usage around this build that has been shared comes with >>>> no warranty. Use with sense. >>>> >>>> fredag 5 maj 2023 kl. 17:23:48 UTC+2 skrev dudek53: >>>> >>>>> Hi. Hacking? Not really following what you mean. Heavy on the >>>>> negativity here. >>>>> I´ll remove the sources for now. They were published for users or >>>>> others to build upon. I have a hard time seeing a better way at this >>>>> stage >>>>> documenting this but others are free to chime in. I keep my personal >>>>> stuff >>>>> secluded from now on. >>>>> This work is mainly done from Erkan so I assume what he posted is as >>>>> unorthodox. Hopefully he´ll fullfill his work when he can according to >>>>> the >>>>> "rules" and guidelines. >>>>> If anyone wants to play with my changes they can contact me and i´ll >>>>> help or share findings in that case. >>>>> Have a great weekend all. >>>>> /D >>>>> >>>>> fredag 5 maj 2023 kl. 17:05:09 UTC+2 skrev T. Modes: >>>>> >>>>>> dud...@gmail.com schrieb am Freitag, 5. Mai 2023 um 11:38:20 UTC+2: >>>>>> >>>>>> Added sources and diffed the arm64 hugin source against latest >>>>>> official sources here. Maybe helps to follow changes from Erkan and me: >>>>>> https://bitbucket.org/Dannephoto/hugin/src/master/ >>>>>> >>>>>> >>>>>> sorry, but it does not help. This is hacking that it works for *you* >>>>>> only and not for any other. >>>>>> >>>>>> Instead of cloning the existing repository you copied all files to a >>>>>> new git repo. Now the whole history is lost. Also it is unknown on which >>>>>> changeset it is based. >>>>>> >>>>>> Next, in one changeset you copied the files from the official hugin >>>>>> repo. In the next changeset you add your changes and at the same time >>>>>> you >>>>>> revert a lot of changes to an earlier changeset of the Hugin repo- which >>>>>> is >>>>>> also unknown. >>>>>> So the changeset is more complicated than necessary. It contains your >>>>>> changes and a lot of unrelated and unnecessary changes at the same time. >>>>>> This makes it very confusing to see your changes only. >>>>>> >>>>>> Hugins build system is connected with the mercurial repo. By >>>>>> switching to git you break this and need to add a file which is >>>>>> (intentional) not under revision control in mercurial. (There are >>>>>> special >>>>>> ways to handle the releases, but these should not be used in development >>>>>> in >>>>>> between.) >>>>>> >>>>>> Next your changes in the source code break the compilation on all >>>>>> other platforms -> "works for me" is not enough. The changes must not >>>>>> break >>>>>> compilation (and running) on other systems. >>>>>> >>>>>> Also randomly changing numbers and sign in the source code without >>>>>> understanding what you do only that it works in *your* single use case >>>>>> is >>>>>> not acceptable. I mentioned this already to you but you have ignored >>>>>> this. >>>>>> >>>>>> Also changing lines in the script and then commenting out the same >>>>>> line is a bad style and makes the diff more confuse than needed. >>>>>> >>>>>> Beside all these mentioned issue it would be recommend to split the >>>>>> changes into small chunks: e.g. one changeset with only changes to the >>>>>> build script, a second one with the needed code changes. >>>>>> >>>>>> Combined it is very difficult to review your changes because of all >>>>>> these mentioned points. >>>>>> Currently it can't applied to official repo because it breaks >>>>>> existing code. >>>>>> >>>>>> -- >>>> A list of frequently asked questions is available at: >>>> http://wiki.panotools.org/Hugin_FAQ >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "hugin and other free panoramic software" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to hugin-ptx+...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/hugin-ptx/e23c72ba-9242-4622-acde-163c72bc8839n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/hugin-ptx/e23c72ba-9242-4622-acde-163c72bc8839n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> >>> >>> -- >>> -- >>> Luis Henrique Camargo Quiroz >>> http://luishcq.br.tripod.com - http://www.christusrex.org/www2/cantgreg >>> http://panoramaslh.net/ >>> >>> -- >>> A list of frequently asked questions is available at: >>> http://wiki.panotools.org/Hugin_FAQ >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "hugin and other free panoramic software" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to hugin-ptx+...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/hugin-ptx/CAEKSoZbcrTL%3DnoHkR0XqRQgBY_-Ys1EUhg0cpYhRFGg_SFrv4A%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/hugin-ptx/CAEKSoZbcrTL%3DnoHkR0XqRQgBY_-Ys1EUhg0cpYhRFGg_SFrv4A%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/9fe7c5b5-12db-459b-87f2-ce5833f67b4fn%40googlegroups.com.
