if such toolchain can be adopted for Android NDK applications.
The NDK build system is certainly no the best, I would like to easily
use CMake or autotools.
The Android NDK uses arm-eabi-4.2.1 GCC toolchain.
Don't I get things wrong?
--
Best regards,
Sergey Rudchenko
--
de
it?
>
>
For instance a block device for your HDD is missing. You can look at
lspci to determine whether your SATA controller is found.
Though, this can be done via dmesg as well. Pretty like any other lspci
info :)
--
Best regards,
Sergey Rudchenko
--
devel mailing list
devel@lists.
/usr/lib/libusb-0.1.so.4.
>
> I have not checked whether there are other cases.
>
>
What if we link the lspci and lsusb as static binaries? That would allow
us not to break the filesystem architecture and have usable tools.
--
Best regards
Sergey Rudchenko
--
devel mailing list
e. Things should only be revived if there are actual users in
> need of the software.
How hard it will be to resurrect any of these if someone needs? Does
that mean packaging from scratch?
--
Best regards,
Sergey Rudchenko
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedor
le-port PATA133 interface (rev b1)
--
Best regards,
Sergey Rudchenko
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
p ownership of this, but would welcome any
> co-maintainers that want to help out (in particular helping triage all
> the bugs opened for it).
>
> Later,
> /B
>
I'd like to help you with the triage and maintenance.
--
Best regards,
Sergey Rudchenko
--
devel mailing l
