Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #163067 > unrolled thread

eagle-lin64-7.5.0.run, won't

Back to article view | Back to linux.debian.user

Contents

  eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-15 00:40 +0100
    Re: eagle-lin64-7.5.0.run, won't Brandon Vincent <Brandon.Vincent@asu.edu> - 2016-01-15 01:40 +0100
      Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-15 03:40 +0100
    Re: eagle-lin64-7.5.0.run, won't Anders Andersson <pipatron@gmail.com> - 2016-01-15 06:10 +0100
      Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-15 06:30 +0100
    Re: eagle-lin64-7.5.0.run, won't Chris Bannister <cbannister@slingshot.co.nz> - 2016-01-16 05:40 +0100
      Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-16 07:10 +0100
        Re: eagle-lin64-7.5.0.run, won't Lisi Reisz <lisi.reisz@gmail.com> - 2016-01-16 11:10 +0100
          Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-16 12:00 +0100
            Re: eagle-lin64-7.5.0.run, won't Brandon Vincent <Brandon.Vincent@asu.edu> - 2016-01-16 14:10 +0100
              Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-16 18:20 +0100
                Re: eagle-lin64-7.5.0.run, won't Joe <joe@jretrading.com> - 2016-01-17 01:50 +0100
                  Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-17 02:30 +0100
                    Re: eagle-lin64-7.5.0.run, won't Joe <joe@jretrading.com> - 2016-01-17 15:50 +0100
                      Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-17 23:30 +0100
                        Re: eagle-lin64-7.5.0.run, won't Lisi Reisz <lisi.reisz@gmail.com> - 2016-01-17 23:40 +0100
            Re: eagle-lin64-7.5.0.run, won't Curt <curty@free.fr> - 2016-01-16 17:00 +0100
              Re: eagle-lin64-7.5.0.run, won't Brandon Vincent <Brandon.Vincent@asu.edu> - 2016-01-16 17:10 +0100
                Re: eagle-lin64-7.5.0.run, won't Curt <curty@free.fr> - 2016-01-16 17:20 +0100
                  Re: eagle-lin64-7.5.0.run, won't Brandon Vincent <Brandon.Vincent@asu.edu> - 2016-01-16 17:30 +0100
                    Re: eagle-lin64-7.5.0.run, won't Brandon Vincent <Brandon.Vincent@asu.edu> - 2016-01-16 17:50 +0100
                      Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-16 18:50 +0100
                      Re: eagle-lin64-7.5.0.run, won't <tomas@tuxteam.de> - 2016-01-17 14:10 +0100
                    Re: eagle-lin64-7.5.0.run, won't Curt <curty@free.fr> - 2016-01-16 17:50 +0100
              Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-16 18:30 +0100
                Re: eagle-lin64-7.5.0.run, won't Lisi Reisz <lisi.reisz@gmail.com> - 2016-01-16 23:50 +0100
                  Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-17 02:20 +0100
                    Re: eagle-lin64-7.5.0.run, won't Lisi Reisz <lisi.reisz@gmail.com> - 2016-01-17 03:10 +0100
                  Re: eagle-lin64-7.5.0.run, won't <tomas@tuxteam.de> - 2016-01-17 14:10 +0100
                    Re: eagle-lin64-7.5.0.run, won't Lisi Reisz <lisi.reisz@gmail.com> - 2016-01-17 15:00 +0100
                Re: eagle-lin64-7.5.0.run, won't David Wright <deblis@lionunicorn.co.uk> - 2016-01-17 04:30 +0100
                  Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-17 05:50 +0100
                Re: eagle-lin64-7.5.0.run, won't Chris Bannister <cbannister@slingshot.co.nz> - 2016-01-17 15:20 +0100
                  Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-17 23:30 +0100
                    Re: eagle-lin64-7.5.0.run, won't Lisi Reisz <lisi.reisz@gmail.com> - 2016-01-17 23:40 +0100
                    Re: eagle-lin64-7.5.0.run, won't Chris Bannister <cbannister@slingshot.co.nz> - 2016-01-19 11:00 +0100
                      Re: eagle-lin64-7.5.0.run, won't Lisi Reisz <lisi.reisz@gmail.com> - 2016-01-19 12:40 +0100
                        Re: eagle-lin64-7.5.0.run, won't Darac Marjal <mailinglist@darac.org.uk> - 2016-01-19 14:10 +0100
                          Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-19 15:50 +0100
                        Re: eagle-lin64-7.5.0.run, won't Chris Bannister <cbannister@slingshot.co.nz> - 2016-01-19 18:00 +0100
                      Re: eagle-lin64-7.5.0.run, won't Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-01-19 14:00 +0100
                        Re: eagle-lin64-7.5.0.run, won't Gene Heskett <gheskett@shentel.net> - 2016-01-19 15:50 +0100

Page 1 of 3  [1] 2 3  Next page →

#163067 — eagle-lin64-7.5.0.run, won't

Greetings all;

Since the gEDA kit in the repo's seems to be rather broken, I thought I'd 
give eagle another chance, so I downloaded, from the cadsoft site, the 
latest 64 bit linux installer, but can't find a help file, and obviously 
I am not training my monkeys correctly.

Has anyone else had any luck, running it after convincing the installer 
where you wanted it installed?

I have cd'd to its base directory, and exported EAGLEDIR=`pwd' so it 
shows in that shells env report, but it can't find its executable with 
both hands, prefering to give me a 
gene@coyote:~/eagle-7.5.0$ bin/eagle
bash: bin/eagle: No such file or directory

Clues? I'm confused enough without this.

Thanks folks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [next] | [standalone]

#163072

On Thu, Jan 14, 2016 at 4:37 PM, Gene Heskett <gheskett@shentel.net> wrote:
> Has anyone else had any luck, running it after convincing the installer
> where you wanted it installed?

I just tried installing Eagle manually and had no problems on a clean
install of Debian 8.

Is your Debian install 64-bit? What is the output of uname(1)?

Brandon Vincent

[toc] | [prev] | [next] | [standalone]

#163078

On Thursday 14 January 2016 19:38:34 Brandon Vincent wrote:

> On Thu, Jan 14, 2016 at 4:37 PM, Gene Heskett <gheskett@shentel.net> 
wrote:
> > Has anyone else had any luck, running it after convincing the
> > installer where you wanted it installed?
>
> I just tried installing Eagle manually and had no problems on a clean
> install of Debian 8.
>
> Is your Debian install 64-bit? What is the output of uname(1)?
>
> Brandon Vincent
ATM,
gene@coyote:~/gaf/charge-pump-bucket$ uname -a
Linux coyote 3.16.0-0.bpo.4-amd64 #1 SMP Debian 
3.16.7-ckt20-1+deb8u2~bpo70+1 (2016-01-03) x86_64 GNU/Linux

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#163084

On Fri, Jan 15, 2016 at 12:37 AM, Gene Heskett <gheskett@shentel.net> wrote:
> Since the gEDA kit in the repo's seems to be rather broken, I thought I'd
> give eagle another chance

While I had no problems using Eagle on 64-bit Debian, I did not like
running closed software. A couple of months ago I switched to KiCad,
and I do not regret it. Some things are not as polished, but some
things are much better. There are things that are pretty bad, but a
huge benefit is that all developers acknowledge this, and are actively
working on improving whatever is bad, instead of the common "no, we
like it the way it is" mindset. Not to mention that CERN is devoting
resources to it.

The package available in Debian 8 is somewhat old because they just
recently released a new stable version after many years of
development. Personally I build it from the "bleeding edge" sources.
The website is http://kicad-pcb.org/ and instructions for downloading
and building should be available on the website.

[toc] | [prev] | [next] | [standalone]

#163085

On Friday 15 January 2016 00:06:51 Anders Andersson wrote:

> On Fri, Jan 15, 2016 at 12:37 AM, Gene Heskett <gheskett@shentel.net> 
wrote:
> > Since the gEDA kit in the repo's seems to be rather broken, I
> > thought I'd give eagle another chance
>
> While I had no problems using Eagle on 64-bit Debian, I did not like
> running closed software. A couple of months ago I switched to KiCad,
> and I do not regret it. Some things are not as polished, but some
> things are much better. There are things that are pretty bad, but a
> huge benefit is that all developers acknowledge this, and are actively
> working on improving whatever is bad, instead of the common "no, we
> like it the way it is" mindset. Not to mention that CERN is devoting
> resources to it.
>
> The package available in Debian 8 is somewhat old because they just
> recently released a new stable version after many years of
> development. Personally I build it from the "bleeding edge" sources.
> The website is http://kicad-pcb.org/ and instructions for downloading
> and building should be available on the website.

Thats great news. I may see about doing that after I get back from a 
sawbones appointment tomorrow.

The issued version for wheezy just doesn't have it, too small a parts 
library but I do think the promise is there with sufficient TLC.

I threw this 6 part schematic together in repo version of gschem tonight, 
but when I went to process it for pcb processing, it turned out that 4 
of the 6 parts from the part library I used, had no footprint data, and 
I've not grokked how to add those attributes to the .sch file yet.  Info 
seems hard to come by, so I've subbed to their list in hopes I can make 
sense of the problem and state it clearly enough to elicit some 
help/advice on how to do that.

Thanks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#163133

On Thu, Jan 14, 2016 at 06:37:49PM -0500, Gene Heskett wrote:
> Greetings all;
> 
> Since the gEDA kit in the repo's seems to be rather broken, I thought I'd 
> give eagle another chance, so I downloaded, from the cadsoft site, the 
> latest 64 bit linux installer, but can't find a help file, and obviously 
> I am not training my monkeys correctly.
> 
> Has anyone else had any luck, running it after convincing the installer 
> where you wanted it installed?
> 
> I have cd'd to its base directory, and exported EAGLEDIR=`pwd' so it 
                                                  ^^^^^^^^^^^^^^
Is that verbatim? I'd put an actual absolute path there. The second
'tic' is not a backtick.

Do backsticks actually work in this case?

> shows in that shells env report, but it can't find its executable with 
> both hands, prefering to give me a 
> gene@coyote:~/eagle-7.5.0$ bin/eagle
> bash: bin/eagle: No such file or directory
> 
> Clues? I'm confused enough without this.

You could try and use the find command to see where it actually is.
I use a locate variant e.g.

# apt-cache show mlocate

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

[toc] | [prev] | [next] | [standalone]

#163138

On Friday 15 January 2016 23:35:53 Chris Bannister wrote:

> On Thu, Jan 14, 2016 at 06:37:49PM -0500, Gene Heskett wrote:
> > Greetings all;
> >
> > Since the gEDA kit in the repo's seems to be rather broken, I
> > thought I'd give eagle another chance, so I downloaded, from the
> > cadsoft site, the latest 64 bit linux installer, but can't find a
> > help file, and obviously I am not training my monkeys correctly.
> >
> > Has anyone else had any luck, running it after convincing the
> > installer where you wanted it installed?
> >
> > I have cd'd to its base directory, and exported EAGLEDIR=`pwd' so it
>
>                                                   ^^^^^^^^^^^^^^
> Is that verbatim? I'd put an actual absolute path there. The second
> 'tic' is not a backtick.
>
Probably a typu Chris.  Ancient fingers & all that. It does show 
correctly in an env query.

> Do backsticks actually work in this case?

Sure!

> > shows in that shells env report, but it can't find its executable
> > with both hands, prefering to give me a
> > gene@coyote:~/eagle-7.5.0$ bin/eagle
> > bash: bin/eagle: No such file or directory
> >
> > Clues? I'm confused enough without this.
>
> You could try and use the find command to see where it actually is.
> I use a locate variant e.g.

Whats the matter with "ls -laR", its right there where I said it was.  
Even has exec perms.

> # apt-cache show mlocate

Point being, I gave up on eagle.  gEDA to the rescue, and I already have 
some very nearly working gcode from gEDA/pcb. Some fine tuning to do 
like 10x bigger solder pads for the outside world connections, and 
potentially about a 50% shrink as I want to make several of these by 
step & repeat. I need 3 instantly, and there may be a potential market 
for a few.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#163142

On Saturday 16 January 2016 06:06:48 Gene Heskett wrote:
> > > shows in that shells env report, but it can't find its executable
> > > with both hands, prefering to give me a
> > > gene@coyote:~/eagle-7.5.0$ bin/eagle
> > > bash: bin/eagle: No such file or directory
> > >
> > > Clues? I'm confused enough without this.
> >
> > You could try and use the find command to see where it actually is.
> > I use a locate variant e.g.
>
> Whats the matter with "ls -laR", its right there where I said it was.  
> Even has exec perms.

So its full path is /home/gene/eagle-7.5.0/bin/eagle, not /bin/eagle?

Lisi

[toc] | [prev] | [next] | [standalone]

#163145

On Saturday 16 January 2016 05:05:22 Lisi Reisz wrote:

> On Saturday 16 January 2016 06:06:48 Gene Heskett wrote:
> > > > shows in that shells env report, but it can't find its
> > > > executable with both hands, prefering to give me a
> > > > gene@coyote:~/eagle-7.5.0$ bin/eagle
> > > > bash: bin/eagle: No such file or directory
> > > >
> > > > Clues? I'm confused enough without this.
> > >
> > > You could try and use the find command to see where it actually
> > > is. I use a locate variant e.g.
> >
> > Whats the matter with "ls -laR", its right there where I said it
> > was.   Even has exec perms.
>
> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not /bin/eagle?
>
> Lisi

I was cd'd to /home/gene/eagle-7.5.0 and the command issued was 
bin/eagle, which is perfectly legal syntax.

FWIW, I even tried the full path, same error.  And I could cd into bin 
and eagle was visible in an ls listing, but wasn't found by an ./eagle

But eagle has always been selective about how it runs on linux.
I poked around on the cadsoft site but could not find a link to their 
forum, so I couldn't ask them.  Which is crazy because I am getting an 
email from the forum sw for every post.  But you can't post via email.

Just one of the many reasons I don't like forums.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#163147

On Sat, Jan 16, 2016 at 3:49 AM, Gene Heskett <gheskett@shentel.net> wrote:
> I was cd'd to /home/gene/eagle-7.5.0 and the command issued was
> bin/eagle, which is perfectly legal syntax.

Gene,

Could you post the output of ldd /home/gene/eagle-7.5.0 for us to see?

Brandon Vincent

[toc] | [prev] | [next] | [standalone]

#163163

On Saturday 16 January 2016 08:06:25 Brandon Vincent wrote:

> On Sat, Jan 16, 2016 at 3:49 AM, Gene Heskett <gheskett@shentel.net> 
wrote:
> > I was cd'd to /home/gene/eagle-7.5.0 and the command issued was
> > bin/eagle, which is perfectly legal syntax.
>
> Gene,
>
> Could you post the output of ldd /home/gene/eagle-7.5.0 for us to see?
>
> Brandon Vincent

gene@coyote:~/eagle-7.5.0$ ldd /home/gene/eagle-7.5.0/
ldd: /home/gene/eagle-7.5.0/: not regular file
gene@coyote:~/eagle-7.5.0$ ldd /home/gene/eagle-7.5.0/bin
ldd: /home/gene/eagle-7.5.0/bin: not regular file
gene@coyote:~/eagle-7.5.0$ ldd /home/gene/eagle-7.5.0/bin/eagle
	not a dynamic executable

But as I said in a PM, its moot, gEDA has come to the rescue.

Now, if ALL the gEDA suite was brought up to date, the repo versions are 
positively ancient, I think it would have been easier. I was able to 
build the latest pcb, V-1.99z, but dependency hell ate any attempts to 
build the newer schematic capture front ends.  So I had to resort to a 
hand edit occasionally with a text editor.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#163185

On Sat, 16 Jan 2016 12:13:14 -0500
Gene Heskett <gheskett@shentel.net> wrote:


> 
> But as I said in a PM, its moot, gEDA has come to the rescue.
> 
> Now, if ALL the gEDA suite was brought up to date, the repo versions
> are positively ancient, I think it would have been easier. I was able
> to build the latest pcb, V-1.99z, but dependency hell ate any
> attempts to build the newer schematic capture front ends.  So I had
> to resort to a hand edit occasionally with a text editor.
> 

What features of the latest and greatest do you need? I haven't used
anything in 20140316 that wasn't in 20110918, and I don't recall any
significant bugs then. This:

http://www.jre-systems.co.uk/pcbs/images/RCP-1.png
http://minibroadcastcameras.co.uk/oem/images/slideshow/Panel52-top.png

was created in late 2007, with whatever version was current at the time.
To be fair, I didn't use schematic capture then, I didn't have a
schematic for this board until after I made it, and to this day the
schematic is hand-drawn in pencil...

I have used schematic capture (gschem and gsch2pcb) for everything
since 2007, with no significant problems. I've used whatever version
was current in sid.

The autorouter has probably improved, but if you're doing anything with
power, you won't want to autoroute anyway. I pretty well only use
two-layer boards, and the last time I tried the autorouter, I could
barely see the tracks for vias. The earlier versions couldn't do a
photo-realistic rendering of the board, but that's only a bit of icing
on the cake, not a show-stopper.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#163187

On Saturday 16 January 2016 19:41:45 Joe wrote:

> On Sat, 16 Jan 2016 12:13:14 -0500
>
> Gene Heskett <gheskett@shentel.net> wrote:
> > But as I said in a PM, its moot, gEDA has come to the rescue.
> >
> > Now, if ALL the gEDA suite was brought up to date, the repo versions
> > are positively ancient, I think it would have been easier. I was
> > able to build the latest pcb, V-1.99z, but dependency hell ate any
> > attempts to build the newer schematic capture front ends.  So I had
> > to resort to a hand edit occasionally with a text editor.
>
> What features of the latest and greatest do you need? I haven't used
> anything in 20140316 that wasn't in 20110918, and I don't recall any
> significant bugs then. This:
>
> http://www.jre-systems.co.uk/pcbs/images/RCP-1.png
> http://minibroadcastcameras.co.uk/oem/images/slideshow/Panel52-top.png
>
> was created in late 2007, with whatever version was current at the
> time. To be fair, I didn't use schematic capture then, I didn't have a
> schematic for this board until after I made it, and to this day the
> schematic is hand-drawn in pencil...
>
> I have used schematic capture (gschem and gsch2pcb) for everything
> since 2007, with no significant problems. I've used whatever version
> was current in sid.
>
Bugs in the gcode exporter are my main beefs. In the gcode output for 
bottom.ngc, with spot drilling enabled, it outputs a line for each of 
the holes, but fills the first 6 of those lines with X0 Y0, so it pecks 
at the lower right corner 6 times, and then spots the rest of the holes 
just fine.

Then, in the mill/drill file, it ignored the request for inches, outputs 
mm's, including the command that puts the LCNC interpretor into the mm's 
mode. But then when I check the file times, it was not even regenerated 
that last time I exported the gcode.  So theres 4 bugs, the 4th one 
being that the gcode exporter fills everything in the boxes for its data 
translations, in with what I have to assume is mm data for everything 
that ought to be inches.

But this is stuff I should take to the geda-user list, which I just sent 
a sub message to join. I do not for a millisecond, think this is a 
debian problem.

> The autorouter has probably improved, but if you're doing anything
> with power, you won't want to autoroute anyway. I pretty well only use
> two-layer boards, and the last time I tried the autorouter, I could
> barely see the tracks for vias. The earlier versions couldn't do a
> photo-realistic rendering of the board, but that's only a bit of icing
> on the cake, not a show-stopper.

I clicked on it, several times after I had arranged things by hand, and 
it never did a thing except waste 1.5 seconds spinning its wheels.

Now, to put this almost back on topic, the first $80 bytes of the 
bin/eagle file are:  Humm, so much for that, khexedit will not do a 
mouse copy/paste.  Luverly.  Anyway it does say ELF in the first 5 or 6 
bytes. Looks like a linux ext-something file to me.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#163214

On Sat, 16 Jan 2016 20:28:50 -0500
Gene Heskett <gheskett@shentel.net> wrote:


> >  
> Bugs in the gcode exporter are my main beefs. In the gcode output for 
> bottom.ngc, with spot drilling enabled, it outputs a line for each of 
> the holes, but fills the first 6 of those lines with X0 Y0, so it
> pecks at the lower right corner 6 times, and then spots the rest of
> the holes just fine.
> 
I see, you're probably in a small minority, so more likelihood of
finding bugs. I've only ever produced Gerber files to send away to PCB
production houses, which I think is what nearly all users do.

> 
> But this is stuff I should take to the geda-user list, which I just
> sent a sub message to join. I do not for a millisecond, think this is
> a debian problem.
> 
Yes, they are very active and will usually have a quick turnround. I've
had some minor issues which were sorted out by direct email with
developers.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#163228

On Sunday 17 January 2016 09:46:36 Joe wrote:

> On Sat, 16 Jan 2016 20:28:50 -0500
>
> Gene Heskett <gheskett@shentel.net> wrote:
> > Bugs in the gcode exporter are my main beefs. In the gcode output
> > for bottom.ngc, with spot drilling enabled, it outputs a line for
> > each of the holes, but fills the first 6 of those lines with X0 Y0,
> > so it pecks at the lower right corner 6 times, and then spots the
> > rest of the holes just fine.
>
> I see, you're probably in a small minority, so more likelihood of
> finding bugs. I've only ever produced Gerber files to send away to PCB
> production houses, which I think is what nearly all users do.
>
> > But this is stuff I should take to the geda-user list, which I just
> > sent a sub message to join. I do not for a millisecond, think this
> > is a debian problem.
>
> Yes, they are very active and will usually have a quick turnround.
> I've had some minor issues which were sorted out by direct email with
> developers.

I method I don't 100% care for, Joe, because such messages never get into 
the list archives.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#163229

On Sunday 17 January 2016 22:21:38 Gene Heskett wrote:
> On Sunday 17 January 2016 09:46:36 Joe wrote:
> > On Sat, 16 Jan 2016 20:28:50 -0500
> >
> > Gene Heskett <gheskett@shentel.net> wrote:
> > > Bugs in the gcode exporter are my main beefs. In the gcode output
> > > for bottom.ngc, with spot drilling enabled, it outputs a line for
> > > each of the holes, but fills the first 6 of those lines with X0 Y0,
> > > so it pecks at the lower right corner 6 times, and then spots the
> > > rest of the holes just fine.
> >
> > I see, you're probably in a small minority, so more likelihood of
> > finding bugs. I've only ever produced Gerber files to send away to PCB
> > production houses, which I think is what nearly all users do.
> >
> > > But this is stuff I should take to the geda-user list, which I just
> > > sent a sub message to join. I do not for a millisecond, think this
> > > is a debian problem.
> >
> > Yes, they are very active and will usually have a quick turnround.
> > I've had some minor issues which were sorted out by direct email with
> > developers.
>
> I method I don't 100% care for, Joe, because such messages never get into
> the list archives.

Why do they need to be in the list archives?  Getting them in the list 
archives doesn't solve the problem if there is a bug.  And once the bug is 
patched, they don't need to be in the archives.

Lisi

[toc] | [prev] | [next] | [standalone]

#163151

On 2016-01-16, Gene Heskett <gheskett@shentel.net> wrote:
>>
>> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not /bin/eagle?
>>
>> Lisi
>
> I was cd'd to /home/gene/eagle-7.5.0 and the command issued was 
> bin/eagle, which is perfectly legal syntax.

Not if bin is not in your path it isn't.

Otherwise, the message from bash is:

bash: eagle: command not found

not

bash: /bin/eagle: No such file or directory

> FWIW, I even tried the full path, same error.  And I could cd into bin 
> and eagle was visible in an ls listing, but wasn't found by an ./eagle

[toc] | [prev] | [next] | [standalone]

#163153

On Sat, Jan 16, 2016 at 8:57 AM, Curt <curty@free.fr> wrote:
> Not if bin is not in your path it isn't.

You should probably read [1].

It is legal syntax.

[1] http://mywiki.wooledge.org/BashFAQ/028

Brandon Vincent

[toc] | [prev] | [next] | [standalone]

#163154

On 2016-01-16, Brandon Vincent <Brandon.Vincent@asu.edu> wrote:
> On Sat, Jan 16, 2016 at 8:57 AM, Curt <curty@free.fr> wrote:
>> Not if bin is not in your path it isn't.
>
> You should probably read [1].
>
> It is legal syntax.

> [1] http://mywiki.wooledge.org/BashFAQ/028

I don't see what you're referring to in there.

> Brandon Vincent
>
>


-- 

[toc] | [prev] | [next] | [standalone]

#163155

On Sat, Jan 16, 2016 at 9:14 AM, Curt <curty@free.fr> wrote:
> I don't see what you're referring to in there.

Eagle installs itself into your home directory under a folder called
"eagle-7.5.0". Inside this folder is the "bin" folder in which the
Eagle executable is stored. If you are in the ~/eagle-7.5.0 directory,
typing "bin/eagle" should launch Eagle. Bash will launch an executable
with only a relative path. It's only when you specify no path, that ./
becomes necessary (assuming a normal $PATH).

Brandon Vincent

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web