https://bugs.kde.org/show_bug.cgi?id=477044
Austin English changed:
What|Removed |Added
CC||austinengl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=461855
Austin English changed:
What|Removed |Added
CC||austinengl...@gmail.com
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=427969
--- Comment #10 from Austin English ---
(In reply to Mark Wielaard from comment #8)
> So I see both examples are for 32bit Debian packages (i386 and arm32). Is
> this an 32bit only issue or are you seeing the same for 64bit packages?
Just trie
https://bugs.kde.org/show_bug.cgi?id=427969
--- Comment #6 from Austin English ---
(In reply to Mark Wielaard from comment #5)
> Thanks for including the files, this is really odd the main ELF file has
> both a .gnu_debuglink section and a .gnu_debugaltlink section, but no .debug
>
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #33 from Austin English ---
To follow up, I misunderstood the scope of Remi's work.
The patchset *does* work for DWARF symbols in PE binaries in modern wine (i.e.,
with wine having a mingw compiled ntdll).
PDB support is a separate
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #32 from Austin English ---
Hi Remi,
Using both wine patches:
https://source.winehq.org/patches/data/196764
https://source.winehq.org/patches/data/196765
and valgrind patches:
https://sourceforge.net/p/valgrind/mailman/message/37164939
https://bugs.kde.org/show_bug.cgi?id=427969
--- Comment #4 from Austin English ---
Created attachment 133681
--> https://bugs.kde.org/attachment.cgi?id=133681=edit
armv7l library
I also see this with 32-bit arm(v7l):
--10058-- WARNING: Serious error when reading debug info
--10058-- W
https://bugs.kde.org/show_bug.cgi?id=427969
--- Comment #3 from Austin English ---
austin@debian-desktop ~/src/valgrind (master) $ readelf -S
/usr/lib/i386-linux-gnu/libbrotlidec.so.1.0.9
There are 27 section headers, starting at offset 0xc1b0:
Section Headers:
[Nr] Name Type
https://bugs.kde.org/show_bug.cgi?id=427969
--- Comment #2 from Austin English ---
Created attachment 132556
--> https://bugs.kde.org/attachment.cgi?id=132556=edit
.debug files
There are a few .debug files listed for this package, so I included all of
them.
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=427969
Austin English changed:
What|Removed |Added
Attachment #132554|.so file|libbrotlidec.so.1.0.9
description
https://bugs.kde.org/show_bug.cgi?id=427969
--- Comment #1 from Austin English ---
Created attachment 132554
--> https://bugs.kde.org/attachment.cgi?id=132554=edit
.so file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427969
Bug ID: 427969
Summary: debuginfo section duplicates a section in the main ELF
file
Product: valgrind
Version: unspecified
Platform: Debian testing
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #30 from Austin English ---
Created attachment 128946
--> https://bugs.kde.org/attachment.cgi?id=128946=edit
compiled test/pdb
(In reply to Jefferson Carpenter from comment #29)
> (In reply to Austin English from comment #28)
>
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #28 from Austin English ---
Created attachment 128170
--> https://bugs.kde.org/attachment.cgi?id=128170=edit
the impossible happened
Upon manual review, it didn't assert, but the impossible happened:
PUTI(136:8xI8)[t1,0] = 0x0
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #27 from Austin English ---
No assertions so far (running still, up to d3d8:visual).
Stacktraces look good. Lots of (valid) warnings for missing symbols in wine:
symbol table size is 0. Not reading debug information for
/home/austin
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #24 from Austin English ---
Getting a failed assertion in some tests:
valgrind: m_debuginfo/debuginfo.c:694 (check_CFSI_related_invariants):
Assertion '!ranges_overlap(map->avma, map->size, map2->avma, map2->size)'
failed.
valg
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #23 from Austin English ---
I usually use -p1, so not sure what was wrong..anyway, recently tried again,
with a clean tree, and it applies fine, so yeah, it was something on my end.
With the patch, I see an improvement using badfree.c from
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #20 from Austin English ---
(In reply to Jefferson Carpenter from comment #19)
> Created attachment 126977 [details]
> Hackish patch: Add read_pe_debug_info: v2
>
> Fixed some of the most significant lies from my first patch
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #16 from Austin English ---
I recently tested llvm-mingw (from https://github.com/mstorsjo/llvm-mingw/),
and built wine with llvm's pdb debug symbols. That gives similar results to gnu
mingw:
==23786== Invalid read of size 2
==23786
https://bugs.kde.org/show_bug.cgi?id=416779
Bug ID: 416779
Summary: valgrind: m_debuginfo/debuginfo.c:454
(discard_or_archive_DebugInfo): Assertion
'!di->have_dinfo || is_DebugInfo_active(di)' failed.
Product: valgrind
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #15 from Austin English ---
As of wine-4.6, wine now supports building its dlls with mingw:
https://source.winehq.org/git/wine.git/commitdiff/a3cf86a18446e9d7df4e045b83d3aa3d9193512a
the plan is to eventually make that the default
https://bugs.kde.org/show_bug.cgi?id=350228
--- Comment #9 from Austin English ---
Created attachment 119495
--> https://bugs.kde.org/attachment.cgi?id=119495=edit
add DRM_IOCTL_I915_GEM_THROTTLE
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=350228
--- Comment #8 from Austin English ---
Created attachment 119494
--> https://bugs.kde.org/attachment.cgi?id=119494=edit
Patch: mention strace as a data source for syscall/ioctl information
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=350228
Austin English changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=350228
--- Comment #6 from Austin English ---
(In reply to Austin English from comment #5)
> I asked in the intel-gfx and xorg IRC channels about these ioctls, and the
> answers were basically "try newer Valgrind" and "look at the
https://bugs.kde.org/show_bug.cgi?id=400538
Austin English changed:
What|Removed |Added
CC||austinengl...@gmail.com
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=253657
--- Comment #24 from Austin English ---
(In reply to Daniel Lehman from comment #23)
> > 0030:err:seh:NtRaiseException Unhandled exception code c01d flags 0
> > addr 0x7bc95b63
>
> that's probably the iretq instruction fr
https://bugs.kde.org/show_bug.cgi?id=253657
--- Comment #22 from Austin English ---
That said, it's still an improvement. Without the patchset, I get:
austin@laptop:~$ /opt/valgrind/bin/valgrind /opt/oldwow64/wine-4.0-rc1/bin/wine
leakage.exe ; echo $?
preloader: Warning: failed to reserve range
https://bugs.kde.org/show_bug.cgi?id=253657
--- Comment #21 from Austin English ---
(In reply to Daniel Lehman from comment #20)
> Created attachment 118764 [details]
> leakage.exe and pdb
>
> attached tested with:
> - Visual Studio 2017 (15.9.8)
> - wine 4.3
>
https://bugs.kde.org/show_bug.cgi?id=253657
--- Comment #19 from Austin English ---
(In reply to Daniel Lehman from comment #18)
> Created attachment 114891 [details]
> simple test case for wine64 pdb
Hi Daniel,
Would you mind attaching a pre-built binary? I'd like to test this, but I
https://bugs.kde.org/show_bug.cgi?id=395991
--- Comment #9 from Austin English ---
(In reply to Julian Seward from comment #8)
> (In reply to Austin English from comment #7)
> > > Austin, can you show me the source of the signal handler involved?
> >
> > Ye
https://bugs.kde.org/show_bug.cgi?id=395991
--- Comment #7 from Austin English ---
(In reply to Julian Seward from comment #6)
> (In reply to Austin English from comment #5)
> > While the situation has changed, it still differs from what I see on amd64.
> > Log attached.
>
https://bugs.kde.org/show_bug.cgi?id=395991
--- Comment #5 from Austin English ---
Created attachment 115058
--> https://bugs.kde.org/attachment.cgi?id=115058=edit
valgrind output
While the situation has changed, it still differs from what I see on amd64. Log
attached.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=395991
--- Comment #2 from Austin English ---
4:49:22 AM austin_laptop if someone with decent understanding of
kernel32/heap.c has a few minutes, I'd appreciate if someone could help me
answer Julian's questions from https://bugs.kde.org/show_bug.cgi?id
https://bugs.kde.org/show_bug.cgi?id=332917
Austin English changed:
What|Removed |Added
CC||austinengl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=344802
Austin English changed:
What|Removed |Added
CC||austinengl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=395991
Austin English changed:
What|Removed |Added
Platform|Other |Compiled Sources
--- Comment #1 from Austin
https://bugs.kde.org/show_bug.cgi?id=395991
Bug ID: 395991
Summary: wine's unit tests enter a signal delivery loop under
valgrind on armv7l when SIGSEGV is used
Product: valgrind
Version: 3.14 SVN
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=266035
Austin English changed:
What|Removed |Added
CC||austinengl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=395777
--- Comment #1 from Austin English ---
That seems to be
#define FBT_BREAKPOINT 0xe7f000f0
according to
https://github.com/F-Stack/f-stack/blob/master/freebsd/arm/include/trap.h
There's only a few more in that header, so it may be worth
https://bugs.kde.org/show_bug.cgi?id=395777
Bug ID: 395777
Summary: disInstr(arm): unhandled instruction: 0xE7F000F0
(wine, dlls/msvcp90/tests/misc.c)
Product: valgrind
Version: 3.14 SVN
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=253657
Austin English changed:
What|Removed |Added
CC||austinengl...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=338252
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
CC||aust
https://bugs.kde.org/show_bug.cgi?id=387686
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- C
https://bugs.kde.org/show_bug.cgi?id=387686
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=387686
Bug ID: 387686
Summary: valgrind-3.13.0 tests on Gentoo fail with glibc-2.26
(work with glibc-2.25).
Product: valgrind
Version: 3.13.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #15 from Austin English <austinengl...@gmail.com> ---
(In reply to Julian Seward from comment #14)
> Landed, c470e0c23c6c79deec943cb6a111b572fc86dbba.
Thanks for the quick fix!
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #13 from Austin English <austinengl...@gmail.com> ---
Created attachment 108909
--> https://bugs.kde.org/attachment.cgi?id=108909=edit
output with patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #12 from Austin English <austinengl...@gmail.com> ---
Created attachment 108908
--> https://bugs.kde.org/attachment.cgi?id=108908=edit
output without patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #11 from Austin English <austinengl...@gmail.com> ---
(In reply to Julian Seward from comment #10)
> Created attachment 108896 [details]
> TPIDRURW support for 32-bit arm
>
> This runs the test program shown in comment
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #7 from Austin English <austinengl...@gmail.com> ---
Re arm/thumb:
so you said it's arm encoding. I noticed that configure.ac
requires thumb? Do both get used?
yes, most of wine should be arm
what's thumb used for?
Windows Apps are
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #6 from Austin English <austinengl...@gmail.com> ---
(In reply to Julian Seward from comment #4)
> (In reply to Julian Seward from comment #3)
> > IIUC, TPIDRURW is a 32 bit register that can be both read and
> > wr
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #2 from Austin English <austinengl...@gmail.com> ---
Forgot to include, some background on why we're doing that:
https://patchwork.kernel.org/patch/2536641/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386425
--- Comment #1 from Austin English <austinengl...@gmail.com> ---
(stretch)austin@localhost:~/src/valgrind$ uname -a
Linux localhost 3.14.0 #1 SMP PREEMPT Wed Oct 25 21:59:24 PDT 2017 armv7l
GNU/Linux
(stretch)austin@localhost:~/src/valgrind
https://bugs.kde.org/show_bug.cgi?id=386425
Bug ID: 386425
Summary: running valgrind + wine on armv7l gives illegal opcode
Product: valgrind
Version: 3.14 SVN
Platform: Compiled Sources
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=382978
--- Comment #2 from Austin English <austinengl...@gmail.com> ---
Forgot to mention in first comment; the PDB format is now publicly documented,
at https://github.com/Microsoft/microsoft-pdb
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=382515
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=382978
--- Comment #1 from Austin English <austinengl...@gmail.com> ---
Created attachment 106999
--> https://bugs.kde.org/attachment.cgi?id=106999=edit
makecert.pdb
I'm also attaching a small pdb file that may be easier to analyze.
--
You are
https://bugs.kde.org/show_bug.cgi?id=382978
Bug ID: 382978
Summary: valgrind: LOAD_PDB_DEBUGINFO: \032 header character
not found. possible invalid/unsupported pdb file
format
Product: valgrind
Version: 3.14 SVN
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #12 from Austin English <austinengl...@gmail.com> ---
(In reply to Philippe Waroquiers from comment #11)
> Note that the patch is compiling on linux, but is completely untested.
> So, expect fire, smoke and explosions ...
Tha
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #8 from Austin English <austinengl...@gmail.com> ---
(In reply to Philippe Waroquiers from comment #6)
> The valgrind code expects something very precise as a header.
> See function static void* find_pdb_header( vo
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #7 from Austin English <austinengl...@gmail.com> ---
Created attachment 106926
--> https://bugs.kde.org/attachment.cgi?id=106926=edit
debug log 2
with --trace-symtab=yes --trace-symtab-patt=*mscorlib*
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #5 from Austin English <austinengl...@gmail.com> ---
Forgot to say, first line of mingw64's pdb is:
BSJB PDB V1.0
first character is \042
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #4 from Austin English <austinengl...@gmail.com> ---
(In reply to Philippe Waroquiers from comment #3)
> This find_pdb_header is searching for a specific character '\032'
> and the string "Microsoft C/C++"
> I
https://bugs.kde.org/show_bug.cgi?id=382515
--- Comment #2 from Austin English <austinengl...@gmail.com> ---
Created attachment 106785
--> https://bugs.kde.org/attachment.cgi?id=106785=edit
debug log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382515
Bug ID: 382515
Summary: valgrind: "Assertion 'di->have_dinfo' failed." on
wine's dlls/mscoree/tests/mscoree.c
Product: valgrind
Version: 3.14 SVN
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #11 from Austin English <austinengl...@gmail.com> ---
@Henri,
I've attached logs use radeonsi_dri.so instead of swrast (which is what I was
using before investigating the issue). This contains the repe instruction as
before.
I'v
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #10 from Austin English <austinengl...@gmail.com> ---
Created attachment 105950
--> https://bugs.kde.org/attachment.cgi?id=105950=edit
radeonsi_dri_64.so
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #9 from Austin English <austinengl...@gmail.com> ---
Created attachment 105949
--> https://bugs.kde.org/attachment.cgi?id=105949=edit
radeonsi_dri_32.so
Had to use xz, bzip2 was over the limit.
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #8 from Austin English <austinengl...@gmail.com> ---
Created attachment 105948
--> https://bugs.kde.org/attachment.cgi?id=105948=edit
log with march disabled, using radeonsi
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #7 from Austin English <austinengl...@gmail.com> ---
Created attachment 105947
--> https://bugs.kde.org/attachment.cgi?id=105947=edit
log with march enabled, using radeonsi
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #6 from Austin English <austinengl...@gmail.com> ---
So, while testing again, I realized I hadn't rerun the test with software
rendering (the full valgrind run and individual test runs are two different
scripts, and the later wasn't f
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #5 from Austin English <austinengl...@gmail.com> ---
Created attachment 105937
--> https://bugs.kde.org/attachment.cgi?id=105937=edit
swrast_dir64.so
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #4 from Austin English <austinengl...@gmail.com> ---
Created attachment 105936
--> https://bugs.kde.org/attachment.cgi?id=105936=edit
swrast_dir32.so
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #3 from Austin English <austinengl...@gmail.com> ---
Created attachment 105935
--> https://bugs.kde.org/attachment.cgi?id=105935=edit
this time, without -march=corei7
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=380869
--- Comment #2 from Austin English <austinengl...@gmail.com> ---
Created attachment 105934
--> https://bugs.kde.org/attachment.cgi?id=105934=edit
full bad output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380869
Bug ID: 380869
Summary: valgrind has issues with mesa comiled with
CFLAGS="-march=corei7"
Product: valgrind
Version: 3.13 SVN
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=365327
--- Comment #15 from Austin English <austinengl...@gmail.com> ---
(In reply to Louis Brunner from comment #12)
> Created attachment 104964 [details]
> macOS Sierra incomplete support
>
> I have been working on a patch to su
https://bugs.kde.org/show_bug.cgi?id=365327
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
CC||aust
https://bugs.kde.org/show_bug.cgi?id=339017
--- Comment #10 from Austin English <austinengl...@gmail.com> ---
(In reply to Rhys Kidd from comment #8)
> We have another user, Austin, who is testing some Wine-specific patches and
> will aim to run Wine's unit tests under Valg
https://bugs.kde.org/show_bug.cgi?id=349804
--- Comment #10 from Austin English <austinengl...@gmail.com> ---
(In reply to Austin English from comment #9)
> (In reply to Austin English from comment #8)
> > Created attachment 94210 [details]
> > wine+valgrind output
> >
https://bugs.kde.org/show_bug.cgi?id=349804
--- Comment #9 from Austin English <austinengl...@gmail.com> ---
(In reply to Austin English from comment #8)
> Created attachment 94210 [details]
> wine+valgrind output
>
> Using wine-1.7.50-26-g6038e2a and valgrind-3.11.0-SVN-r155
https://bugs.kde.org/show_bug.cgi?id=211031
--- Comment #14 from Austin English <austinengl...@gmail.com> ---
(In reply to Austin English from comment #13)
> This is also relevant again for wine-gecko. Upstream Firefox moved to
> require Visual Studio 2013+, and those newer format PDB
https://bugs.kde.org/show_bug.cgi?id=295084
--- Comment #10 from Austin English <austinengl...@gmail.com> ---
(In reply to Rhys Kidd from comment #9)
> I'm almost certain there's a problem with your local copy of Xcode or with
> multiple versions of Xcode tripping up.
>
> It
https://bugs.kde.org/show_bug.cgi?id=376027
Bug ID: 376027
Summary: wine's comdlg32/filedlg.c test hangs under valgrind
Product: valgrind
Version: 3.13 SVN
Platform: Compiled Sources
URL:
https://bugs.kde.org/show_bug.cgi?id=350228
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=354809
--- Comment #1 from Austin English <austinengl...@gmail.com> ---
With:
austin@debian-laptop:~/src/valgrind$ ./vg-in-place --version -v
valgrind-3.13.0.SVN-16209-vex-3299
the error message has improved (64-bit valgrind, 32-bit binary):
austin@
https://bugs.kde.org/show_bug.cgi?id=344139
--- Comment #2 from Austin English <austinengl...@gmail.com> ---
To give a bit more info (and for myself in the future ;).
This is still present in development wine (wine-1.9.24-105-g1d3b944) and
valgrind (valgrind-3.13.0.SVN, #define VGSVN
https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #29 from Austin English <austinengl...@gmail.com> ---
(In reply to Philippe Waroquiers from comment #28)
> Strange that the git-svn version does not show a M(odified) marker.
Yeah, I noticed that too. I'll try to remember to f
https://bugs.kde.org/show_bug.cgi?id=295084
--- Comment #8 from Austin English <austinengl...@gmail.com> ---
To be more explicit:
Austins-Mac-mini:~ austin$ xcode-select --install
xcode-select: note: install requested for command line developer tools
Austins-Mac-mini:~ austin$ ls /usr/
https://bugs.kde.org/show_bug.cgi?id=295084
--- Comment #7 from Austin English <austinengl...@gmail.com> ---
(In reply to Rhys Kidd from comment #6)
> Austin,
>
> Before you do, can you please confirm that you have the latest Xcode Command
> Line Tools installed? It is
https://bugs.kde.org/show_bug.cgi?id=295084
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
CC||aust
https://bugs.kde.org/show_bug.cgi?id=354809
Austin English <austinengl...@gmail.com> changed:
What|Removed |Added
CC||aust
https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #27 from Austin English <austinengl...@gmail.com> ---
(In reply to Austin English from comment #26)
> Created attachment 102512 [details]
> try 10, extra sanity checks
>
> try 9 works for me, but I put some extra sanity ch
https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #26 from Austin English <austinengl...@gmail.com> ---
Created attachment 102512
--> https://bugs.kde.org/attachment.cgi?id=102512=edit
try 10, extra sanity checks
try 9 works for me, but I put some extra sanity checks in.
https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #22 from Austin English <austinengl...@gmail.com> ---
(In reply to Ivo Raisr from comment #20)
> Patch #6 seems to be working well. I tested it on Solaris, inside SVN tree,
> outside and after 'make dist'.
>
> In ad
https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #17 from Austin English <austinengl...@gmail.com> ---
(In reply to Philippe Waroquiers from comment #16)
> Created attachment 102468 [details]
> try 6 : modified to have vgversion.h also handled as part of make dist
>
>
https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #13 from Austin English <austinengl...@gmail.com> ---
(In reply to Austin English from comment #12)
> How commonly are tarballs created/used for random SVN revisions rather than
> releases?
>
> To be frank, I'm no
https://bugs.kde.org/show_bug.cgi?id=352395
--- Comment #12 from Austin English <austinengl...@gmail.com> ---
How commonly are tarballs created/used for random SVN revisions rather than
releases?
To be frank, I'm not very experienced with makefiles, and the current changes
have alread
99 matches
Mail list logo
