Package: libdw-dev
Version: 0.189-4
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com
libdw-dev:
Description: libdw1 development libraries and header files
This is really poor choice of a description. It does not provide any
actual information. Like what libdw1 is?
Usually Description
:16, Jonathan McDowell wrote:
>
> On Thu, Feb 25, 2021 at 06:12:07PM +, Witold Baryluk wrote:
> > No problem.
> >
> > Both ways (single package or separate package) are fine for me. I did
> > a single package in the PR draft because it was way easier to do.
10:27:54AM +, Witold Baryluk wrote:
> > Have you had time to look at my MR draft I sent before?
>
> This fell off my radar because of the build problems due to not pulling
> in the extra required patches. I've done some cleanup of the package
> build so the extra Debian patche
Hi Jonathan.
Have you had time to look at my MR draft I sent before?
Cheers.
On Fri, 22 Jan 2021 at 16:45, Witold Baryluk wrote:
>
> A simple (but not-too-simple) test is now included in MR:
>
> https://salsa.debian.org/electronics-team/toolchains/gcc-xtensa-lx106/-/merge_requ
A simple (but not-too-simple) test is now included in MR:
https://salsa.debian.org/electronics-team/toolchains/gcc-xtensa-lx106/-/merge_requests/1/diffs
On Fri, 22 Jan 2021 at 15:52, Witold Baryluk wrote:
>
> Yes, for the basic enablement I do have a draft patch (very simple):
>
a look.
On Fri, 22 Jan 2021 at 15:42, Jonathan McDowell wrote:
>
> On Fri, Jan 22, 2021 at 02:22:11PM +, Witold Baryluk wrote:
> > So, it does appear that /usr/src/gcc-10/gcc-10.2.0-dfsg.tar.xz from
> > gcc-10-source 10.2.1-6 ,
> > doesn't have these patches appli
So, it does appear that /usr/src/gcc-10/gcc-10.2.0-dfsg.tar.xz from
gcc-10-source 10.2.1-6 ,
doesn't have these patches applied. And the patches need to be applied
manually after unpacking.
/usr/src/gcc-10/debian/README.source provides some information, but it
is a bit tricky:
Indeed. It looks like debian/patches/*.patch are not used
user@debian:~/xtensa-d/gcc-xtensa-lx106-8$ dpkg-buildpackage --no-sign
dpkg-buildpackage: info: source package gcc-xtensa-lx106
dpkg-buildpackage: info: source version 8
dpkg-buildpackage: info: source distribution unstable
Hi.,
I was trying to build cross-compiler for xtensa with D compiler
enabled, and there is one things that makes that fail.
https://salsa.debian.org/toolchain-team/gcc/-/blob/master/debian/rules.unpack#L154
overwrites gcc/doc/gcc-common.texi with minimal version (probably some
dfsg reasons).
Package: gdc-10
Version: 10.1.0-1
Severity: normal
It is common to provide unittests for module in the module, but without
main, so the module can be used as a library.
For this reasons, to test just one module one need to provide a dummy main
function when linking.
-fmain does this
Package: gdc-10
Version: 10.1.0-1
Severity: normal
This is for gdc-10. I tested it with gdc-9 and it works without a crash.
$ cat bench.d
// =
import std.conv : to;
int main(string[] args) {
return cast(int)to!float(args[1]);
}
// ===
$
$ gdc-10 -flto -O2 -fno-weak -o
It look this might be already fixed upstream:
https://github.com/dlang/druntime/pull/2620
https://github.com/dlang/druntime/commit/0723a38a858e83a9c5c0d43a0400571ef2a0
and could explain why ldc is showing correct values.
On Sat, 9 May 2020 at 22:57, Witold Baryluk wrote:
>
> Packag
Package: gdc-10
Version: 10.1.0-1
Severity: normal
Dear Maintainer,
import std.stdio;
import core.cpuid;
void main() {
writefln("CPU: threads_per_cpu=%d; cores_per_cpu=%d; ht=%s; processor=%s",
threadsPerCPU(), coresPerCPU(), hyperThreading(), processor());
}
# Using
Package: gdc
Version: 4:9.2.1-3.1
Severity: normal
Dear Maintainer,
According to language spec:
https://dlang.org/spec/function.html#main
"""
19.20 main() Function
For console programs, main() serves as the entry point. It gets called
after all the module initializers are run, and after any
Package: gdc
Version: 4:9.2.1-3.1
Followup-For: Bug #808724
This bug seems to be fixed long time ago:
$ gdc example.d
dlang.d:10:9: error: switch statement without a default; use 'final switch' or
add 'default: assert(0);' or add 'default: break;'
10 | switch (1) {
$
So, bug can be
Package: gdc
Version: 4:9.2.1-3.1
Severity: normal
According to man page for gdc(1):
-debuglib
Specify the debug library to use instead of libphobos when linking.
This option
has no effect unless the -g option was also given on the command
line. Options
Package: gdc-8
Version: 8.3.0-6
Followup-For: Bug #914470
Still broken in 8.3.0-6
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-2-amd64
Package: gdc-8
Version: 8.2.0-9
Severity: normal
# cat perf_min.d
```
module perf_min;
void run(alias prep = delegate() {})() {
prep();
}
void main() {
run!()();
}
```
$ gdc perf_min.d
perf_min.d: In function ‘run’:
perf_min.d:3:5: internal compiler error: in get_frame_for_symbol, at
updated
version in Depends: libc6, or other libc6 releated package.
--
Witold Baryluk
JID: witold.baryluk // jabster.pl
signature.asc
Description: Digital signature
model : EV6
cpu variation : 7
...
Regards.
I can provide access to this machine over ssh.
[1]
http://cdimage.debian.org/cdimage/archive/5.0.8/alpha/iso-cd/debian-508-alpha-netinst.iso
[2] http://d-i.debian.org/daily-images/alpha/
--
Witold Baryluk
JID: witold.baryluk
Package: libgcj-doc
Version: 4.2.2-3
Severity: minor
libgcj-doc is big, and when using apt for install/upgrade
it says that will use about 300MB of hard disk space,
(or only few MB if upgrading). But if i have previous version
of libgcj-doc, 50MB of free disk space, and apt says that
10MB of
21 matches
Mail list logo
