More details:
https://github.com/Homebrew/homebrew/issues/21778
On Mon, Feb 23, 2015 at 10:56 AM, Adam Wolf
<adamwolf@xxxxxxxxxxxxxxxxxxxx <mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>
wrote:
I am fine building for Core Duo--but it'll be more than just
changing -march, it looks like I'll also have to set the other
optional flags as well, like SSE et al at the bottom of:
https://github.com/Homebrew/homebrew/blob/master/Library/Homebrew/os/mac/hardware.rb
Does anyone on this list own a Core Duo mac? If so I'd like to
just steal the flags that system uses...
Adam Wolf
On Mon, Feb 23, 2015 at 10:53 AM, Johannes Maibaum
<jmaibaum@xxxxxxxxx <mailto:jmaibaum@xxxxxxxxx>> wrote:
Hi,
sounds all reasonable and clear, Garth. Thank you for the
explanation!
Personally, I have no problem in building my own version from
the sources, but I think there
are still quite a bunch of Core2s in Apple machines out there,
so perhaps the nightlies
should go for a more backwards compatibility than i5 and siblings.
Looking here,
https://github.com/Homebrew/homebrew/blob/master/Library/Homebrew/os/mac/hardware.rb
it seems that Homebrew indeed makes different choices for
-march depending on the CPU type
found. So, I think the "best arch for compatibility" then
would probably be the oldest intel
CPU found there, which seems to be Core Duo.
Another solution would of course be to simply state in the
README that the nightlies won't
work on machines lower than i5. As I said, I have no problem
in building Kicad myself. I just
wanted to report my experience with the nightlies, which are
nonetheless a great improvement
for new, unexperienced Mac OSX users.
So again, thank you all for your great work and help!
Best,
Johannes
> Am 23.02.2015 um 17:22 schrieb Adam Wolf
<adamwolf@xxxxxxxxxxxxxxxxxxxx
<mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>:
>
> What's the best arch I should pass for compatibility
reasons--I can do this across the board for the brew dependencies.
>
> Adam Wolf
>
> On Mon, Feb 23, 2015 at 10:04 AM, Garth Corral
<gcorral@xxxxxxxxx <mailto:gcorral@xxxxxxxxx>> wrote:
> The issue here isn’t with pixman, per se, it is down to the
fact that it is being configured and built on one machine with
support for some newer vector instructions, and run on another
who’s cpu does not support those instructions. So long as
it’s built and run on the same machine you would not see this.
>
> In this case there appears at the crash location in
_pixman_setup_combiner_functions_32 of libpixman.dylib:
>
> 000000000001092a vmovq %r8, %xmm0
> 000000000001092f vpunpcklqdq %xmm0, %xmm0, %xmm0 ## xmm0
= xmm0[0,0]
>
> These are AVX (&AVX2) instructions, which aren't supported
in your Core 2 CPU.
>
> I don’t use brew so I can’t say for sure, but I’m guessing
that it's passing -march=native (or more specific) to the
compiler, which because the Core i5 of the build machine
supports AVX, is including those instructions.
>
>
> Garth
>
> > On Feb 23, 2015, at 5:21 AM, Johannes Maibaum
<jmaibaum@xxxxxxxxx <mailto:jmaibaum@xxxxxxxxx>> wrote:
> >
> > Hi,
> >
> > my own build of r5447 just finished and pcbnew does *not*
crash.
> > I decided to change my build flags to match Adam's more
closely, e.g. building without
> > Scripting, here is what the version information *from my
own build* gives now:
> >
> > Application: kicad
> > Version: (2015-02-22 BZR 5447)-product Release build
> > wxWidgets: Version 3.0.2 (debug,UTF-8,compiler with C++
ABI 1002,GCC 4.2.1,STL containers,compatible with 2.8)
> > Platform: Mac OS X (Darwin 14.1.0 x86_64), 64 bit, Little
endian, wxMac
> > Boost version: 1.57.0
> > USE_WX_GRAPHICS_CONTEXT=OFF
> > USE_WX_OVERLAY=ON
> > KICAD_SCRIPTING=OFF
> > KICAD_SCRIPTING_MODULES=OFF
> > KICAD_SCRIPTING_WXPYTHON=OFF
> > USE_FP_LIB_TABLE=HARD_CODED_ON
> > BUILD_GITHUB_PLUGIN=ON
> > KICAD_USE_WEBKIT=OFF
> >
> > So, the only differences between my setup and the nightly
should be, for now:
> >
> > - Boost being 1.57.0 here instead of 1.54.0
> > - cairo built --without-x11 instead of with X11 support.
> >
> > I think that pixmap should be technically the same on my
machine and on Adam's build server,
> > as they both got installed precompiled from Homebrew.
> >
> > But, what came to my mind just now: I built with
CMAKE_OSX_DEPLOYMENT_TARGET set to 10.9
> > (wxWidgets being built with the 10.9 option from the
osx_build_wx script as well), so
> > it should be linked to the newer C++ libraries from Apple,
right? Could this be another
> > hint? I expect Adam to build for a lower OSX Version, like
10.7 or so, right?
> >
> >
> > Best,
> >
> > Johannes
> >
> >> Am 23.02.2015 um 13:54 schrieb Bernhard Stegmaier
<stegmaier@xxxxxxxxxxxxx <mailto:stegmaier@xxxxxxxxxxxxx>>:
> >>
> >> Hi,
> >>
> >> I don't know if it helps... I am building pixman with
MacPorts, and I used to have it compiled with X11, but I
recently switched to use the --without-x11.
> >> For me both work, I don't see what the difference is
(apart from less X11-libraries needed in the bundle when
compiling with --without-x11).
> >>
> >> SSE-wise Core2Duo and i5 should be the same.
> >> But maybe pixman builds with some specific i5
-march/-mcpu settings that don't work on Core2Duo?
> >> But, obviously Adam pulled in a prebuilt binary for this
nightly that also doesn't work for you.
> >> As far as I know homebrew bottled packages should have
generic CFLAGS, so this should have worked then (if the binary
really was bottled with generic CFLAGS).
> >>
> >>
> >> Regards,
> >> Bernhard
> >>
> >> On 2015-02-23 12:40, Johannes Maibaum wrote:
> >>> Hello Adam, Garth, and Bernhard,
> >>> first, the build of last night (r5447) still crashes on
my system with
> >>> the same report pointing towards libpixman.
> >>> My system is an older Mac Book Pro (middle 2010) with
the following base specs:
> >>> Modellname: MacBook Pro
> >>> Modell-Identifizierung: MacBookPro7,1
> >>> Prozessortyp: Intel Core 2 Duo
> >>> Prozessorgeschwindigkeit: 2,4 GHz
> >>> Anzahl der Prozessoren: 1
> >>> Gesamtanzahl der Kerne: 2
> >>> L2-Cache: 3 MB
> >>> With libpixman obviously being the source of trouble, I
looked for
> >>> differences between my own working build system and
Adam's nightlies:
> >>> On my machine, pixman comes as a dependency for cairo,
which I also
> >>> installed via Homebrew, but built with the option
--without-x11.
> >>> pixman itself was installed "bottled", e.g. as a
precompiled binary.
> >>> Seeing that I am obviously the only one having troubles
like this with
> >>> the nightlies, I will build the current Kicad source
tree myself again
> >>> this afternoon, and see if pcbnew will then crash again
or not.
> >>> Best,
> >>> Johannes
> >>>> Am 23.02.2015 um 01:41 schrieb Adam Wolf
<adamwolf@xxxxxxxxxxxxxxxxxxxx
<mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>:
> >>>> So when I reinstalled it, it installed a binary version
without downloading, which means that's very likely what was
installed on there before. I forced it to reinstall from
source--but that is probably going to be different than the
binary version.
> >>>> I will send the build log for pixman over when it is
finished, but we will need the affected users to test out
tonight's nightlies to make sure they're still affected.
> >>>> Adam Wolf
> >>>> On Sun, Feb 22, 2015 at 6:36 PM, Garth Corral
<gcorral@xxxxxxxxx <mailto:gcorral@xxxxxxxxx>> wrote:
> >>>> Yeah, not shipped with OS X. It would be something
that was built. Presuming that the new build configured
exactly like the old build it would be interesting to see.
> >>>> Garth
> >>>>> On Feb 22, 2015, at 3:48 PM, Adam Wolf
<adamwolf@xxxxxxxxxxxxxxxxxxxx
<mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>> wrote:
> >>>>> Interesting. Is this something that comes with OS X?
If not, I installed it with brew. I can uninstall it and
reinstall it, and capture that log.
> >>>>> Let me know.
> >>>>> Adam Wolf
> >>>>> On Feb 22, 2015 5:47 PM, "Garth Corral"
<gcorral@xxxxxxxxx <mailto:gcorral@xxxxxxxxx>> wrote:
> >>>>> More interesting would be the build log for pixman
which, according to the attached log, is coming from
/usr/local/lib.
> >>>>> Garth
> >>>>>> On Feb 22, 2015, at 3:31 PM, Adam Wolf
<adamwolf@xxxxxxxxxxxxxxxxxxxx
<mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>> wrote:
> >>>>>> The builds are being done on a Mac Mini.
> >>>>>> Model Name: Mac mini
> >>>>>> Model Identifier: Macmini6,1
> >>>>>> Processor Name: Intel Core i5
> >>>>>> Processor Speed: 2.5 GHz
> >>>>>> Number of Processors: 1
> >>>>>> Total Number of Cores: 2
> >>>>>> L2 Cache (per Core): 256 KB
> >>>>>> L3 Cache: 3 MB
> >>>>>> Memory: 16 GB
> >>>>>> The official Mac name for it is "Mac Mini (late 2012)".
> >>>>>> Attached is the full build log from Jenkins. Note, I
cleanly rebuild *everything* every time, including wx and
boost and everything, so the log is quite long.
> >>>>>> Adam Wolf
> >>>>>> Cofounder and Engineer
> >>>>>> W&L
> >>>>>> On Sun, Feb 22, 2015 at 4:13 PM, Bernhard Stegmaier
<stegmaier@xxxxxxxxxxxxx <mailto:stegmaier@xxxxxxxxxxxxx>> wrote:
> >>>>>> Sounds reasonable… from a quick look into the source
pixman seems to check for MMX/SSE2/SSE3 and some non-x86
things during configure.
> >>>>>> Maybe the same problem here:
> >>>>>> https://bugs.launchpad.net/kicad/+bug/1424406
> >>>>>> @Adam:
> >>>>>> What is your build machine/cluster?
> >>>>>> Regards,
> >>>>>> Bernhard
> >>>>>>> On 22 Feb 2015, at 21:12, Garth Corral
<gcorral@xxxxxxxxx <mailto:gcorral@xxxxxxxxx>> wrote:
> >>>>>>> I can only speculate, but by the looks of that
stack, I’m going to guess that somewhere in the pixman
rendering code there is conditionally compiled instruction
extensions, such as SSE*, that your cpu does not support. The
nightly builds probably compile this in based on some
configuration test, and your builds do not.
> >>>>>>> What is the cpu type and age of your system?
> >>>>>>> Garth
> >>>>>>>> On Feb 22, 2015, at 11:14 AM, Bernhard Stegmaier
<stegmaier@xxxxxxxxxxxxx <mailto:stegmaier@xxxxxxxxxxxxx>> wrote:
> >>>>>>>> Hi,
> >>>>>>>> OK, didn’t get that.
> >>>>>>>> From my side there is really not much more to help.
> >>>>>>>> The only thing that I could imagine is if Wayne
could do a Debug-Build for you and then you could check if you
still get that crash and if there is some other information we
could get from that.
> >>>>>>>> The bundle is self contained, so apart from the
system libraries (which should be the same on each 10.10.2)
there is in theory nothing on your machine that should break it.
> >>>>>>>> What machine is it?
> >>>>>>>> Something special about it that could cause pixman
to crash on start?
> >>>>>>>> Did you have any special pixman
version/configuration with your build?
> >>>>>>>> Regards,
> >>>>>>>> Bernhard
> >>>>>>>>> On 22.02.2015, at 20:06, Johannes Maibaum
<jmaibaum@xxxxxxxxx <mailto:jmaibaum@xxxxxxxxx>> wrote:
> >>>>>>>>> Hi Bernard,
> >>>>>>>>> sorry, I wasn't clear enough, I think. The version
information I provided with my last email was *not* from the
nightlies. It was from a working built on my machine, e.g. a
build that does *not* crash.
> >>>>>>>>> I thought to provide this information a starting
point for further analysis of the crash with the nightly which
is of course built with Boost 1.54, and from r5441.
> >>>>>>>>> Best,
> >>>>>>>>> Johannes
> >>>>>>>>>> Am 22.02.2015 um 19:22 schrieb Bernhard Stegmaier
<stegmaier@xxxxxxxxxxxxx <mailto:stegmaier@xxxxxxxxxxxxx>>:
> >>>>>>>>>> … I also was too fast with my response, adding
list again…
> >>>>>>>>>>> On 22.02.2015, at 19:21, Bernhard Stegmaier
<stegmaier@xxxxxxxxxxxxx <mailto:stegmaier@xxxxxxxxxxxxx>> wrote:
> >>>>>>>>>>> Hi Johannes,
> >>>>>>>>>>> it is lib-pixmap what seems to be crashing, but
that is weird.
> >>>>>>>>>>> I found some similar reports of crashes with
Mozilla/Firefox/etc., but none of them with a root-cause or
more information.
> >>>>>>>>>>> However, something *is* wrong:
> >>>>>>>>>>>> Boost version: 1.57.0
> >>>>>>>>>>> Adam’s build doesn’t use 1.57, but 1.54
currently being built with KiCad…
> >>>>>>>>>>> And also the build version is not what Adam built:
> >>>>>>>>>>>> Version: (2015-02-06 BZR 5410)-product Release
build
> >>>>>>>>>>> So, whatever you are running, it doesn’t seem to
be the downloaded nightly?
> >>>>>>>>>>> Regards,
> >>>>>>>>>>> Bernhard
> >>>>>>>>>>>> On 22.02.2015, at 19:20, Johannes Maibaum
<jmaibaum@xxxxxxxxx <mailto:jmaibaum@xxxxxxxxx>> wrote:
> >>>>>>>>>>>> Hi Bernhard,
> >>>>>>>>>>>> the crash happens both when starting pcbnew
standalone, and when starting pcbnew or the footprint editor
from the main Kicad app. Unfortunately, I don't have another
Mac to cross check. On my 10.10.2 machine, it crashes every time.
> >>>>>>>>>>>> I did however check my latest own build again,
which has no problems with either pcbnew or the footprint
editor. It was built two weeks ago, from r5410, and with
python scripting enabled. I don't know if this does help you,
but here is the version information string for this working build:
> >>>>>>>>>>>> Application: kicad
> >>>>>>>>>>>> Version: (2015-02-06 BZR 5410)-product Release
build
> >>>>>>>>>>>> wxWidgets: Version 3.0.2 (debug,UTF-8,compiler
with C++ ABI 1002,GCC 4.2.1,STL containers,compatible with 2.8)
> >>>>>>>>>>>> Platform: Mac OS X (Darwin 14.1.0 x86_64), 64
bit, Little endian, wxMac
> >>>>>>>>>>>> Boost version: 1.57.0
> >>>>>>>>>>>> USE_WX_GRAPHICS_CONTEXT=OFF
> >>>>>>>>>>>> USE_WX_OVERLAY=ON
> >>>>>>>>>>>> KICAD_SCRIPTING=ON
> >>>>>>>>>>>> KICAD_SCRIPTING_MODULES=ON
> >>>>>>>>>>>> KICAD_SCRIPTING_WXPYTHON=ON
> >>>>>>>>>>>> USE_FP_LIB_TABLE=HARD_CODED_ON
> >>>>>>>>>>>> BUILD_GITHUB_PLUGIN=ON
> >>>>>>>>>>>> KICAD_USE_WEBKIT=OFF
> >>>>>>>>>>>> Best,
> >>>>>>>>>>>> Johannes
> >>>>>>>>>>>>> Am 22.02.2015 um 18:12 schrieb Bernhard
Stegmaier <stegmaier@xxxxxxxxxxxxx
<mailto:stegmaier@xxxxxxxxxxxxx>>:
> >>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>> does it crash only for standalone pcbnew, or
also for that being launched via KiCad launcher, or both?
> >>>>>>>>>>>>> I justed checked on both my 10.10.1 and
10.10.2 machines and don’t have any problems.
> >>>>>>>>>>>>> The only thing I just noticed is that pcbnew
can’t load a file via KiCad launcher if started from a path
with a space in it (e.g., /Volumes/My Disk/KiCad…) … but yours
seems to be completely another story.
> >>>>>>>>>>>>> Regards
> >>>>>>>>>>>>> Bernhard
> >>>>>>>>>>>>>> On 22 Feb 2015, at 14:05, Johannes Maibaum
<jmaibaum@xxxxxxxxx <mailto:jmaibaum@xxxxxxxxx>> wrote:
> >>>>>>>>>>>>>> Hi Adam,
> >>>>>>>>>>>>>> first, I'd like to thank you, Wayne and
Layne, and of course all the other OSX devs for finally
bringing "official" OSX builds back to the Kicad main page,
great work! This is an amazing improvement for all OSX folks.
> >>>>>>>>>>>>>> But, testing the latest of the nightly
builds, PCBNew and the Footprint editor both crash on startup
on my machine (crash log for PCBNew is attached). All other
apps work fine.
> >>>>>>>>>>>>>> Before installing the nightly, I uninstalled
my own build of Kicad, and I am pretty sure to having wiped
every Kicad file relating to my build (including all the
library folders). But perhaps I have missed something.
> >>>>>>>>>>>>>> I can provide you with more information if
you tell me what to do.
> >>>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>> Johannes
> >>>>>>>>>>>>>> <PCBNew-crashlog-OSX-nightly-Feb-22.txt>
> >>>>>>>>>>>>>>> Am 21.02.2015 um 18:29 schrieb Adam Wolf
<adamwolf@xxxxxxxxxxxxxxxxxxxx
<mailto:adamwolf@xxxxxxxxxxxxxxxxxxxx>>:
> >>>>>>>>>>>>>>> Hi folks,
> >>>>>>>>>>>>>>> You can find the latest OS X nightlies at
http://downloads.kicad-pcb.org/osx/, and Nick linked it from
http://downloads.kicad-pcb.org/osx/.
> >>>>>>>>>>>>>>> There's plenty of work still left to do for
me on Kicad, but I am excited to cross this one off the list.
> >>>>>>>>>>>>>>> I'll be idling on the IRC channel more
actively to help support users with this.
> >>>>>>>>>>>>>>> I'll be announcing on the Kicad user list
shortly.
> >>>>>>>>>>>>>>> Thanks everyone! Even though this was a lot
of work from us at Wayne and Layne, what we did was only a
drop in the bucket compared to what has already been done by
the dev team and the OS X devs!
> >>>>>>>>>>>>>>> Adam Wolf
> >>>>>>>>>>>>>>> Cofounder and Engineer
> >>>>>>>>>>>>>>> W&L
> >>>>>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>>>>> Mailing list:
https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>>>>>>>>>>> Post to :
kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>>>>>>>>>>>>> Unsubscribe :
https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>>>>>>>>>>> More help :
https://help.launchpad.net/ListHelp
> >>>>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>>>> Mailing list:
https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>>>>>>>>>> Post to :
kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>>>>>>>>>>>> Unsubscribe :
https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>>>>>>>>>> More help : https://help.launchpad.net/ListHelp
> >>>>>>>> _______________________________________________
> >>>>>>>> Mailing list:
https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>>>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>>>>>> Unsubscribe :
https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>>>> More help : https://help.launchpad.net/ListHelp
> >>>>>> _______________________________________________
> >>>>>> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>> More help : https://help.launchpad.net/ListHelp
> >>>>>>
<consoleText.txt.zip>_______________________________________________
> >>>>>> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>>> More help : https://help.launchpad.net/ListHelp
> >>>>> _______________________________________________
> >>>>> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>>> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>>> More help : https://help.launchpad.net/ListHelp
> >>>> _______________________________________________
> >>>> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>>> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>>> More help : https://help.launchpad.net/ListHelp
> >>> _______________________________________________
> >>> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >>> More help : https://help.launchpad.net/ListHelp
> >>
> >> _______________________________________________
> >> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> >> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> >> More help : https://help.launchpad.net/ListHelp
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> > Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> > Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> > More help : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
<mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> More help : https://help.launchpad.net/ListHelp
>
>
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
