You seem to think you can just grab anything with the words STM32 and it will work for the STM32F103C8 with roger's core? Can you just grab stuff that mentions atmel and usb and expect it to compile and run atmega32u4 usb code that you intend to run on an attiny using the arduino core?
Those articles you point to have nothing to do with the libmaple core here. They are specifically talking about an STM32F4 which is completely different than the STM32F103 we are using.
I think the problem here is a language barrier. I don't speak German so I'm probably not explaining this stuff well.
I gave you the
simplest installation steps to get roger's/libmaple going on a linux box. Step by step. I then gave you instructions that show you how to
modify your boards.txt so that it would allow you to use the native USB even though you are uploading via the usart rom serial bootloader. However, you seem to have already got your self in a state of brokeness. You are mixing and matching instructions to the point that your .arduino15 directory is broken.
My suggestion:
back up and save your ~/.arduino15
back up and save your ~/Arduino
delete ~/.arduino15
delete ~/Arduino
follow the instructions I specified
get a blink example working
ignore the fact that the /var/log/syslog is spewing messages about your bluepill USB device.
follow the instructions for modifying your boards.txt to add the defines
load the Asciitable example onto your bluepill
tail -f /var/log/syslog
make sure the boot0 pin on the bluepill is back to running mode.
unplug and replug your bluepill usb serial connection
... the whole problem with the native usb.. you aren't going to get a serial terminal running fast enough to catch the asciitable output
... you will come back when the modemmanager grabs the /dev/ttyACM0 and thinks it should be able to make calls
... you will come back when the permissions prevent you from opening /dev/ttyACM0
... you will come back and complain you see no output
It sounds to me that you should just be happy with the usart rom serial bootloader. Gain some experience using the bluepill with that setup and then tackle native USB in the future.
(here i go adding another monkey wrench to success) Maybe by the time you are getting comfortable with the STM32F1 the core being developed by ST will have native USB support for the bluepill and it will just be a simple install from the boards manager.