How is this a meme?

lost my right to vote, can only work in fast food now, am subject to search and seizure with out warrant.

This pretty much sums up what happens when you get born in north Korea (except the jobs are worse than fast food)

They were still worse off than western europe

To quote a random politician who was talking about the eastern Germany wall: "Capitalism might not be perfect but at least we don't have to build a wall to keep our citizens in"

Just check what make install does

I demand the source and context

I'm sorting by new and somehow this showed up

24

Personally I like GNOME guidelines

I don't know of any besides for material 3 and GNOME

If it's a software issue just tell them to install gnu/linux. That might make their issues worse but at least you converted someone to the ~~cult~~ religion!

6
submitted 1 year ago* (last edited 1 year ago) by original_ish_name@latte.isnot.coffee to c/vim@lemmy.ml

Solution:

  1. Make all command substition in a make done through the assignment operator e.g.
cflags != pkg-config --cflags gtk4
libs != pkg-config --libs gtk4

all:
	gcc $(cflags) -o watch main.c $(libs)

not

all:
	gcc $$(pkg-config --cflags gtk4) -o watch main.c $$(pkg-config --libs gtk4)
  1. add this to your .vimrc: let g:ale_c_parse_makefile = 1

ALE gives me a warning when I use gtk

#include <gtk/gtk.h> /* E: gtk/gtk.h: No such file or directory

This is probably happening because ALE isn't using my compiler flags gcc $( pkg-config --cflags gtk4 ) -o program main.c $( pkg-config --libs gtk4 ) that I stole from the gtk documentation. These compiler flags allow gcc to find gtk/gtk.h even though it is in gtk-4.0/gtk/gtk.h

How do I make ALE aware of my compiler flags?

68
submitted 1 year ago* (last edited 1 year ago) by original_ish_name@latte.isnot.coffee to c/piracy@lemmy.dbzer0.com
  1. Plug in the dvd

  2. Run lsblk to see if it got detected

  3. Run dd if=/dev/cdrom of=dvd.dvd status=progress

  4. You can now play the ripped dvd using mpv: mpv dvd://0/dvd.dvd

If you need to get rid of digital restrictions management, you can try this guide

MOM!!! People are disagreeing with me!!!! :(

Pwease defederate

They're becoming source available

Because you mentioned the GPL:

they are following the technicalities here. The GPL bans stopping people from spreading the source code, but it never explicitly bans requiring people to accept a EULA that does not allow redistribution in order to buy the product

They are legally in the right but it is still shitty

2
submitted 1 year ago* (last edited 1 year ago) by original_ish_name@latte.isnot.coffee to c/postmarketos@lemmy.ml

So I am trying to port postmarketos, I have gotten very far (everything has compiled) but there is an issue during pmbootstrap install

Before you ask I have asked Matrix/IRC

I noticed my SoC has mainline support so I'm mainlining it

Phone specs:

  • Samsung Galaxy A127F
  • Exynos 850 SoC
  • stock bootloader

Logs:

Files used:

What I think is happening:

  • mkbootimg is failing for some reason

What I think can fix it:

  • Disabling it. This wiki page says:

    " generate_bootimg | Set this to true for fastboot device, so the mkinitfs command will generate a boot.img file after creating the initfs. Add mkbootimg as dependency to your device's APKBUILD! "

    I don't know if a phone using samsungs download mode counts as a "fastboot device" I have tried disabling it but heimdall then stopped at 6% I followed the advice of the wiki but then heimdall got stuck at 27%

  • Adding more arguments. The error is error: not enough arguments '/tmp/mkinitfs1981624154/boot.img' so just add the arguments? The problem is I don't know which ones. According to the wiki I could use bootimg_custom_args to add custom arguments, but which custom arguments? And where are the files arguments like --kernel should point to?

Please remind me if I forgot to mention anything and I will happily edit my post :D

Edit: I would just like to say thanks to everyone who has helped me on previous issues and anyone who helps me on any other issue (including this one)

5

GSIs sound like a way to reinvent the square wheel when it comes to uefi

1
submitted 1 year ago* (last edited 1 year ago) by original_ish_name@latte.isnot.coffee to c/linuxphones@lemmy.ml

Phone used for testing (not that I got that far): Samsung Galaxy A127F

Kernel source code used:

  1. Search for "SM-A127F_CIS_13_Opensource.zip" from samsungs website
  2. Move it to somewhere like ~/projects/postmarketos/stock/SM-A127F_CIS_13_Opensource.zip (referred to as $stock from now on)
  3. unzip $stock using unzip $stock command
  4. there should now be a "Kernel.tar.gz" file. Make a new directory called "Kernel" (the path to this directory would be called $kernel from now on.) Move Kernel.tar.gz to $kernel. Extract $kernel by running tar -xf Kernel.tar.gz

As you can guess I couldn't find the kernel in a git repo so I followed the wikis advice of running pmbootstrap samsung-a12 --src=/$kernel

[15:44:27] ERROR: Could not find aport for package: samsung-a12
[15:44:27] See also: <https://postmarketos.org/troubleshooting>
Run 'pmbootstrap log' for details.

well that seems interesting

I didn't find any reference to the error message in the wiki and while I did find a promising google result (proxied through a metasearch engine of course) it was a reddit thread that wasn't archived by the wayback machine

Why this might have happened:

  • the wiki said that if you didn't install pmbootstrap through git the places would change. I didn't install it through git but it might be assuming I did
  • the wiki never said if I had to change anything in "linux-samsung-a12/APKBUILD", so I assumed I didn't need to change anything, maybe I did?

Log:

mirrordir_alpine=edge

[v23.06]
description=Latest release / Recommended for best stability
branch_pmaports=v23.06
branch_aports=3.18-stable
mirrordir_alpine=v3.18

[v22.12]
description=Old release (supported until: 2023-07-07)
branch_pmaports=v22.12
branch_aports=3.17-stable
mirrordir_alpine=v3.17

[v22.06]
description=Old release (unsupported)
branch_pmaports=v22.06
branch_aports=3.16-stable
mirrordir_alpine=v3.16

[v21.12]
description=Old release (unsupported)
branch_pmaports=v21.12
branch_aports=3.15-stable
mirrordir_alpine=v3.15

[v21.06]
description=Old release (unsupported)
branch_pmaports=v21.06
branch_aports=3.14-stable
mirrordir_alpine=v3.14

[v21.03]
description=Old release (unsupported)
branch_pmaports=v21.03
branch_aports=3.13-stable
mirrordir_alpine=v3.13

[v20.05]
description=Old release (unsupported)
branch_pmaports=v20.05
branch_aports=3.12-stable
mirrordir_alpine=v3.12
(012374) [15:03:00] ERROR: Could not find aport for package: samsung-a12
(012374) [15:03:00] See also: <https://postmarketos.org/troubleshooting>
(012374) [15:03:00] Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/pmb/__init__.py", line 63, in main
    getattr(frontend, args.action)(args)
  File "/usr/lib/python3.11/site-packages/pmb/helpers/frontend.py", line 114, in build
    arch_package = args.arch or pmb.build.autodetect.arch(args, package)
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/pmb/build/autodetect.py", line 46, in arch
    aport = pmb.helpers.pmaports.find(args, pkgname)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/pmb/helpers/pmaports.py", line 181, in find
    raise RuntimeError("Could not find aport for package: " +
RuntimeError: Could not find aport for package: samsung-a12

(012382) [15:03:04] % tail -n 60 -F /home/user/.local/var/pmbootstrap/log.txt
(012382) [15:03:04] *** output passed to pmbootstrap stdout, not to this log ***

Operating System used for building: Arch (btw)

It should be called "Lemmy is more fun"

view more: next ›

original_ish_name

joined 1 year ago