Sending Resume

[Engineer - Mgr]

RIC  SIE

Tel   (408)482-2840[EMAIL PROTECTED]  



OBJECTIVE:  STRUCTURAL &  MECHANICAL  DESIGNER

CIVIL, ARCHITECTURAL, TRANSPORTATION  CAD Operator 

EXPERIENCE:

93 - present
DESIGNER, ENGINEER,  CAD MANAGER;  "Mech-Tronic"  

Engineering & Design Service, Project Management & Development.
Preparing technical documentation, calculations, layouts drawings &
propositions. CAD Management and Operations, drafting & redesigning.
Intergraph, MicroStation,  Autodesk, ACAD, Win, Net, Softdesk Mgmt
Civil, Bridges and Structural Design, Plans, Mapping, Detail Freeway
& Roadway, data translation & inserting. Script & CAD automation.
Geological Structures, Viaducts, Freeways, Highways, Shopping Center. 
Architectural and Environmental Projects and cooperation; military
facilities and plans, Cities, Airports, remediation drawings upgrade,
correcting and redesign. Traffic design & problem analyzes-reorganize.
Freeway Design & Drafting Support, Site analyzing for Caltrans,
Architectural, Archeotype & Electrical drawings, "as is" and initial design;  
Develop remediation procedure and equipment for lead painted buildings.
Construction management, Job site inspection, civil & structural support
Mechanical Evaluations - Design - Service and Maintenance; R&D.

EDUCATION:
Institute for Business & Technology, California
CAD Engineer, Programming, Design, Management

Electro - Mechanical College
Mechanical Engineering  -  BS  Degree

DOS, UNIX, MAC, SUN computers;  WP, dBASE, Lotus, Network, Lisp,
Windows & Appl., PFS, Graphics, CAD/CAM, Basic, Fortran, Analyzes.
METRIC,  SOLAR,  AutoCAD/Computer Instructor. Transportation Spec.
Personal Designer, MS Project, MS Works, Excel, Access, C, Script, File
Management, File transfer. Learn quickly, work independly, shift, overtime

Re: Status of non-recursive automake

[John Darrington]

On Tue, Dec 02, 2003 at 07:43:01PM -0600, Bob Friesenhahn wrote:
 Based on my recent experience, non-recursive builds are working very
 well in the current automake release.  Use 'subdir-objects' in
 AUTOMAKE_OPTIONS if you want the objects to be placed at the same
 relative location as the source files.  An issue with the 'clean'
 target has been reported for the case where the makefile is also
 recursive (SUBDIRS is used).  Objects get unnecessary funny naming in
 the case where TARGET_CPPFLAGS is used but this doesn't seem to break
 anything.
 
 Since the '/' in target definitions are not "make" syntax compatible,
 all the '/'s in target definitions need to be manually smashed to '_'.
 This is very tedious and error prone, and is something that Automake
 should fix.
 

Is there anything else that's required?

I made a simple Makefile.am :


AUTOMAKE_OPTIONS=subdir-objects

bin_PROGRAMS=atl
atl_SOURCES=src1_foo.c src2_bar.c

But the resulting Makefile produces: 

make: *** No rule to make target `src1_foo.c', needed by `src1_foo.o'.  Stop

J'

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://wwwkeys.pgp.net or any PGP keyserver for public key.




pgp0.pgp
Description: PGP signature

Re: Status of non-recursive automake

[Bob Friesenhahn]

On Wed, 3 Dec 2003, John Darrington wrote:

> Is non-recursive currently supported in automake or is it still in
> development/ideas stage?  If it's already working, what version do I
> need, and what documentation exists?

Based on my recent experience, non-recursive builds are working very
well in the current automake release.  Use 'subdir-objects' in
AUTOMAKE_OPTIONS if you want the objects to be placed at the same
relative location as the source files.  An issue with the 'clean'
target has been reported for the case where the makefile is also
recursive (SUBDIRS is used).  Objects get unnecessary funny naming in
the case where TARGET_CPPFLAGS is used but this doesn't seem to break
anything.

Since the '/' in target definitions are not "make" syntax compatible,
all the '/'s in target definitions need to be manually smashed to '_'.
This is very tedious and error prone, and is something that Automake
should fix.

Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen

Re: Automake 1.7h uploaded (fourth beta for Automake 1.8)

[Pavel Roskin]

On Tue, 2 Dec 2003, Alexandre Duret-Lutz wrote:

> Hi people,
>
> Due to two last minute new features, we have yet another weekly beta
> of Automake 1.8.  I sincerely hope this is the last one.  If you are
> not blas?, or if you have not had the occasion to test previous
> versions, please give this one a try.

GNU Midnight Commander is OK, just tested it.

One little nitpick.  Either the message about underquoted macros in
aclocal should cause aclocal to fail, or there should be a word "WARNING"
in the message.  I actually mistook this message for the reason why
autogen.sh failed (the reason was unrelated to Automake).  I mean this
code in aclocal.in:

   print STDERR "$file:$.: underquoted definition of $2\n";
   print STDERR "$file:$.: run info '(automake)Extending aclocal'\n"
 . "or see http://sources.redhat.com/automake/";
 . "automake.html#Extending%20aclocal\n"

By the way, wouldn't the "warn" function in Perl more appropriate?  It's
used elsewhere in aclocal.in.  It doesn't add "WARNING" though.

I also hope 1.8 will be released soon.  I cannot wait for m4_include
support.  Many thanks to the Automake team.

-- 
Regards,
Pavel Roskin

Status of non-recursive automake

[John Darrington]

Hi folks,

Is non-recursive currently supported in automake or is it still in
development/ideas stage?  If it's already working, what version do I
need, and what documentation exists?

I've been trying to follow some threads in this list to gleem an
insight, but I joined late ...  so I'd be obliged if someone could
tell me what the status is. 


Thanks,

John


-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://wwwkeys.pgp.net or any PGP keyserver for public key.




pgp0.pgp
Description: PGP signature

it works better

[Billie T. Eldridge]

Title: ad





CLICK
HERE TO READ MORE



No more mail

Automake 1.7h uploaded (fourth beta for Automake 1.8)

[Alexandre Duret-Lutz]

Hi people,

Due to two last minute new features, we have yet another weekly beta
of Automake 1.8.  I sincerly hope this is the last one.  If you are
not blasé, or if you have not had the occasion to test previous
versions, please give this one a try.

You can find this beta here:

ftp://alpha.gnu.org/gnu/automake/automake-1.7h.tar.gz
ftp://alpha.gnu.org/gnu/automake/automake-1.7h.tar.gz.sig
ftp://alpha.gnu.org/gnu/automake/automake-1.7h.tar.bz2
ftp://alpha.gnu.org/gnu/automake/automake-1.7h.tar.bz2.sig

or here:

ftp://sources.redhat.com/pub/automake/automake-1.7h.tar.gz
ftp://sources.redhat.com/pub/automake/automake-1.7h.tar.gz.sig
ftp://sources.redhat.com/pub/automake/automake-1.7h.tar.bz2
ftp://sources.redhat.com/pub/automake/automake-1.7h.tar.bz2.sig

Here are the MD5 checksums:

2ed0df2dc0ba74d0cc55fc8689f1ec22  automake-1.7h.tar.bz2
a8b9311d183345d8c2336a135d270c63  automake-1.7h.tar.gz

Please report bugs to <[EMAIL PROTECTED]>.

Changes between 1.7f and 1.7h:

* New computation of default filenames
  (see the first "New feature" in the full NEWS below).
* Ignore trailing comments in variable definitions
  (automake was confused by `bin_PROGRAMS = foo#bar').
* New machinery that allows Automake to expand variables which are
  part of filenames (as in `CLEANFILES = $(PROJ).info') when it
  processes a list of filenames.  This is currently disabled
  everywhere except in CLEANFILES, because it improves backward
  compatibility in an undocumented hack to support non-distributed
  info files.  However it is nice to have this feature handy, and
  we might turn on this expansion in more places later.

New in 1.7h, since 1.7.9:

* Meta-News

  - The NEWS file is more verbose.

* Requirements

  - Autoconf 2.58 or greater is required.

* New features

  - Default source file names in the absence of a _SOURCES declaration
are made by removing any target extension before appending `.c', so
to make the libtool module `foo.la' from `foo.c', you only need to
do this:

lib_LTLIBRARIES = foo.la
foo_la_LDFLAGS  = -module

For backward compatibility, foo_la.c will be used instead of
foo.c if this file exists or is the explicit target of a rule.
However -Wobsolete will warn about this deprecated naming.

  - AR's `cru' flags are now set in a global ARFLAGS variable instead
of being hard-coded in each $(AR) invocation, so they can be
substituted from configure.ac.  This has been requested by people
dealing with non-POSIX ar implementations.

  - New warning option: -Woverride.  This will warn about any user
target or variable definitions which override Automake
definitions.

  - Texinfo rules back up and restore info files when makeinfo fails.

  - Texinfo rules now support the `html' target.
Running this requires Texinfo 4.0 or greater.

`html' is a new recursive target, so if your package mixes
hand-crafted `Makefile.in's with Automake-generated
`Makefile.in's, you should adjust the former to support (or
ignore) this target so that `make html' recurses successfully.  If
you had a custom `html' rule in your `Makefile.am', it's better to
rename it as `html-local', otherwise your rule will override
Automake's new rule (you can check that by running `automake
-Woverride') and that will stop the recursion to subdirectories.

Last but not least, this `html' rule is declared PHONY, even when
overridden.  Fortunately, it appears that few packages use a
non-PHONY `html' rule.

  - Any file which is m4_included from configure.ac will appear as a
configure and Makefile.in dependency, and will be automatically
distributed.

  - The rules for rebuilding Makefiles and Makefile.ins will now
rebuild all Makefiles and all Makefile.ins at once when one of
configure's dependencies has changed.  This is considerably faster
than previous implementations, where config.status and automake
were run separately in each directory (this still happens when you
change a Makefile.am locally, without touching configure.ac or
friends).  Doing this also solves a longstanding issue: these
rebuild rules failed to work when adding new directories to the
tree, forcing you to run automake manually.

  - For similar reasons, the rules to rebuild configure,
config.status, and aclocal.m4 are now defined in all directories.
Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
CONFIGURE_DEPENDENCIES (undocumented) variables, you should better
define them in all directories.  This is easily done using an
AC_SUBST (make sure you prefix these dependencies with
$(abs_top_srcdir) since this variable will appear at different
levels of the build tree).

  - aclocal will now use `m4_include' instead of copying local m4
files into aclocal.m4.  (Local m4 files are those you ship with
your project, other files will be copied as usual.)

   

Re: failure building HEAD

[Robert Collins]

On Tue, 2003-12-02 at 21:44, Alexandre Duret-Lutz wrote:
> I think this is the problem.  Ben, you cannot write
> `$output.tmp' because when $output is /dev/null a user cannot
> create /dev/null.tmp.  This change breaks the configuration of
> all versions of Automake since 1.6 :(

Yah, so, the right way to do this would be to write to a safe temp file
in /tmp, and then move that to the destination?

Rob
-- 
GPG key available at: .


signature.asc
Description: This is a digitally signed message part

Deciding wether dynamic or static

[JRBCAST]

Hi all,

I am facing a little trouble. I have a library which I am turning
GNUcompliant. It consists on some libraries and many executables.
Librariesget built OK but some programs that use external libraries
don't. Thisis because some of those libraries are only built in a Shared
way sostatic linking is not possible. 

The question is, Can I, in some way, determine if I will be able tobuild
a program in a static and/or dynamic way during compilation time?Is it
compulsory instead, to do it in configuring time? How is it done?Can you
point me to some documentation about the issue?.Thanks very much.

Re: failure building HEAD

[Alexandre Duret-Lutz]

reopen 221483
stop

>>> "Robert" == Robert Collins <[EMAIL PROTECTED]> writes:

 Robert> On Mon, 2003-12-01 at 18:09, Alexandre Duret-Lutz wrote:
 >> >>> "Robert" == Robert Collins <[EMAIL PROTECTED]> writes:
 >> 
 >> [...]
 >> 
 Robert> configure:1847: cd conftest && eval autoconf -o /dev/null conftest.ac
 Robert> autom4te: cannot open /dev/null.tmp: Permission denied
 >> 
 Robert> Is this a 'need to use 2.59' thing? (If so, the error is misleading).
 >> 
 >> It works fine with Autoconf 2.58.   I wonder if your version of Autoconf
 >> is patched, or if autoconf is a wrapper, or something.  I can't see where
 >> this `.tmp' suffix would come from.

 Robert> I'm on debian unstable, so there is a wrapper - but I
 Robert> bypassed it with the same results.

I just updated my Debian packages today and saw this in the
changelog.Debian for autoconf:

autoconf (2.58-7) unstable; urgency=low

  * Make autom4te create files via a temporary followed by a rename, so
that partial writes don't happen.  Closes: #221483.

 -- Ben Pfaff <[EMAIL PROTECTED]>  Tue, 18 Nov 2003 21:43:40 -0800

I think this is the problem.  Ben, you cannot write
`$output.tmp' because when $output is /dev/null a user cannot
create /dev/null.tmp.  This change breaks the configuration of
all versions of Automake since 1.6 :(
-- 
Alexandre Duret-Lutz

playing with recursive libtool static archives

[Marty Leisner]

How do I configure/construct Makefile.am to either:
1) tell libtool to use the --preserve-dup-deps flag
or:
2) be able to switch in the linker flag --whole-archive/no-whole-archive
in the right places.

Everything I tried doesn't seem to work -- beyond hand hacking makefiles
or hand hacking libtool.




marty   [EMAIL PROTECTED]   
Don't  confuse education with schooling.
Milton Friedman to Yogi Berra